System, method, and apparatus for DVSEC for efficient peripheral management

ABSTRACT

Aspects of the embodiments include systems, methods, devices, and computer program products to receive, from the downstream component, an indication of an extended capability; determining, from the indication, one or more configuration parameters for the downstream component; applying the one or more configuration parameters; and performing data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters. The extended capabilities can be indicated by a DVSEC extended capability definition received from a downstream device. The extended capabilities of the downstream component can indicate the number of buses, the port type, the expandability capability, the D3Cold support status, the host router indicator, and/or the safe eject requirements of the downstream component.

BACKGROUND

Interconnects can be used to provide communication between different devices within a system, some type of interconnect mechanism is used. One typical communication protocol for communications interconnects between devices in a computer system is a Peripheral Component Interconnect Express (PCI Express™ (PCIe™)) communication protocol. This communication protocol is one example of a load/store input/output (I/O) interconnect system. The communication between the devices is typically performed serially according to this protocol at very high speeds.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a block diagram for a computing system including a multicore processor.

FIG. 2 is a schematic diagram of an example peripheral component interconnect express (PCIe) link architecture in accordance with embodiments of the present disclosure.

FIG. 3 is a schematic block diagram of a connected system that includes a hierarchy of device connected to a host by a PCIe-compliant link in accordance to embodiments of the present disclosure.

FIG. 4 is a schematic diagram of a DVSEC capabilities definition that includes one or more attribute hint bits in accordance with embodiments of the present disclosure.

FIG. 5 is a process flow diagram for a host device to implement one or more attributes of a downstream component based on a DVSEC capabilities definition in accordance with embodiments of the present disclosure.

FIG. 6 illustrates an embodiment of a computing system including an interconnect architecture.

FIG. 7 illustrates an embodiment of a interconnect architecture including a layered stack.

FIG. 8 illustrates an embodiment of a request or packet to be generated or received within an interconnect architecture.

FIG. 9 illustrates an embodiment of a transmitter and receiver pair for an interconnect architecture.

FIG. 10 illustrates another embodiment of a block diagram for a computing system including a processor.

FIG. 11 illustrates an embodiment of a block for a computing system including multiple processor sockets.

FIG. 12 illustrates another embodiment of a block diagram for a computing system.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth, such as examples of specific types of processors and system configurations, specific hardware structures, specific architectural and micro architectural details, specific register configurations, specific instruction types, specific system components, specific measurements/heights, specific processor pipeline stages and operation etc. in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that these specific details need not be employed to practice the present invention. In other instances, well known components or methods, such as specific and alternative processor architectures, specific logic circuits/code for described algorithms, specific firmware code, specific interconnect operation, specific logic configurations, specific manufacturing techniques and materials, specific compiler implementations, specific expression of algorithms in code, specific power down and gating techniques/logic and other specific operational details of computer system have not been described in detail in order to avoid unnecessarily obscuring the present invention.

Although the following embodiments may be described with reference to energy conservation and energy efficiency in specific integrated circuits, such as in computing platforms or microprocessors, other embodiments are applicable to other types of integrated circuits and logic devices. Similar techniques and teachings of embodiments described herein may be applied to other types of circuits or semiconductor devices that may also benefit from better energy efficiency and energy conservation. For example, the disclosed embodiments are not limited to desktop computer systems or Ultrabooks™. And may be also used in other devices, such as handheld devices, tablets, other thin notebooks, systems on a chip (SOC) devices, and embedded applications. Some examples of handheld devices include cellular phones, Internet protocol devices, digital cameras, personal digital assistants (PDAs), and handheld PCs. Embedded applications typically include a microcontroller, a digital signal processor (DSP), a system on a chip, network computers (NetPC), set-top boxes, network hubs, wide area network (WAN) switches, or any other system that can perform the functions and operations taught below. Moreover, the apparatus', methods, and systems described herein are not limited to physical computing devices, but may also relate to software optimizations for energy conservation and efficiency. As will become readily apparent in the description below, the embodiments of methods, apparatus', and systems described herein (whether in reference to hardware, firmware, software, or a combination thereof) are vital to a ‘green technology’ future balanced with performance considerations.

As computing systems are advancing, the components therein are becoming more complex. As a result, the interconnect architecture to couple and communicate between the components is also increasing in complexity to ensure bandwidth requirements are met for optimal component operation. Furthermore, different market segments demand different aspects of interconnect architectures to suit the market's needs. For example, servers require higher performance, while the mobile ecosystem is sometimes able to sacrifice overall performance for power savings. Yet, it is a singular purpose of most fabrics to provide highest possible performance with maximum power saving. Below, a number of interconnects are discussed, which would potentially benefit from aspects of the invention described herein.

Referring to FIG. 1, an embodiment of a block diagram for a computing system including a multicore processor is depicted. Processor 100 includes any processor or processing device, such as a microprocessor, an embedded processor, a digital signal processor (DSP), a network processor, a handheld processor, an application processor, a co-processor, a system on a chip (SOC), or other device to execute code. Processor 100, in one embodiment, includes at least two cores—core 101 and 102, which may include asymmetric cores or symmetric cores (the illustrated embodiment). However, processor 100 may include any number of processing elements that may be symmetric or asymmetric.

In one embodiment, a processing element refers to hardware or logic to support a software thread. Examples of hardware processing elements include: a thread unit, a thread slot, a thread, a process unit, a context, a context unit, a logical processor, a hardware thread, a core, and/or any other element, which is capable of holding a state for a processor, such as an execution state or architectural state. In other words, a processing element, in one embodiment, refers to any hardware capable of being independently associated with code, such as a software thread, operating system, application, or other code. A physical processor (or processor socket) typically refers to an integrated circuit, which potentially includes any number of other processing elements, such as cores or hardware threads.

A core often refers to logic located on an integrated circuit capable of maintaining an independent architectural state, wherein each independently maintained architectural state is associated with at least some dedicated execution resources. In contrast to cores, a hardware thread typically refers to any logic located on an integrated circuit capable of maintaining an independent architectural state, wherein the independently maintained architectural states share access to execution resources. As can be seen, when certain resources are shared and others are dedicated to an architectural state, the line between the nomenclature of a hardware thread and core overlaps. Yet often, a core and a hardware thread are viewed by an operating system as individual logical processors, where the operating system is able to individually schedule operations on each logical processor.

Physical processor 100, as illustrated in FIG. 1, includes two cores—core 101 and 102. Here, core 101 and 102 are considered symmetric cores, i.e. cores with the same configurations, functional units, and/or logic. In another embodiment, core 101 includes an out-of-order processor core, while core 102 includes an in-order processor core. However, cores 101 and 102 may be individually selected from any type of core, such as a native core, a software managed core, a core adapted to execute a native Instruction Set Architecture (ISA), a core adapted to execute a translated Instruction Set Architecture (ISA), a co-designed core, or other known core. In a heterogeneous core environment (i.e. asymmetric cores), some form of translation, such a binary translation, may be utilized to schedule or execute code on one or both cores. Yet to further the discussion, the functional units illustrated in core 101 are described in further detail below, as the units in core 102 operate in a similar manner in the depicted embodiment.

As depicted, core 101 includes two hardware threads 101 a and 101 b, which may also be referred to as hardware thread slots 101 a and 101 b. Therefore, software entities, such as an operating system, in one embodiment potentially view processor 100 as four separate processors, i.e., four logical processors or processing elements capable of executing four software threads concurrently. As alluded to above, a first thread is associated with architecture state registers 101 a, a second thread is associated with architecture state registers 101 b, a third thread may be associated with architecture state registers 102 a, and a fourth thread may be associated with architecture state registers 102 b. Here, each of the architecture state registers (101 a, 101 b, 102 a, and 102 b) may be referred to as processing elements, thread slots, or thread units, as described above. As illustrated, architecture state registers 101 a are replicated in architecture state registers 101 b, so individual architecture states/contexts are capable of being stored for logical processor 101 a and logical processor 101 b. In core 101, other smaller resources, such as instruction pointers and renaming logic in allocator and renamer block 130 may also be replicated for threads 101 a and 101 b. Some resources, such as re-order buffers in reorder/retirement unit 135, ILTB 120, load/store buffers, and queues may be shared through partitioning. Other resources, such as general purpose internal registers, page-table base register(s), low-level data-cache and data-TLB 115, execution unit(s) 140, and portions of out-of-order unit 135 are potentially fully shared.

Processor 100 often includes other resources, which may be fully shared, shared through partitioning, or dedicated by/to processing elements. In FIG. 1, an embodiment of a purely exemplary processor with illustrative logical units/resources of a processor is illustrated. Note that a processor may include, or omit, any of these functional units, as well as include any other known functional units, logic, or firmware not depicted. As illustrated, core 101 includes a simplified, representative out-of-order (OOO) processor core. But an in-order processor may be utilized in different embodiments. The OOO core includes a branch target buffer 120 to predict branches to be executed/taken and an instruction-translation buffer (I-TLB) 120 to store address translation entries for instructions.

Core 101 further includes decode module 125 coupled to fetch unit 120 to decode fetched elements. Fetch logic, in one embodiment, includes individual sequencers associated with thread slots 101 a, 101 b, respectively. Usually core 101 is associated with a first ISA, which defines/specifies instructions executable on processor 100. Often machine code instructions that are part of the first ISA include a portion of the instruction (referred to as an opcode), which references/specifies an instruction or operation to be performed. Decode logic 125 includes circuitry that recognizes these instructions from their opcodes and passes the decoded instructions on in the pipeline for processing as defined by the first ISA. For example, as discussed in more detail below decoders 125, in one embodiment, include logic designed or adapted to recognize specific instructions, such as transactional instruction. As a result of the recognition by decoders 125, the architecture or core 101 takes specific, predefined actions to perform tasks associated with the appropriate instruction. It is important to note that any of the tasks, blocks, operations, and methods described herein may be performed in response to a single or multiple instructions; some of which may be new or old instructions. Note decoders 126, in one embodiment, recognize the same ISA (or a subset thereof). Alternatively, in a heterogeneous core environment, decoders 126 recognize a second ISA (either a subset of the first ISA or a distinct ISA).

In one example, allocator and renamer block 130 includes an allocator to reserve resources, such as register files to store instruction processing results. However, threads 101 a and 101 b are potentially capable of out-of-order execution, where allocator and renamer block 130 also reserves other resources, such as reorder buffers to track instruction results. Unit 130 may also include a register renamer to rename program/instruction reference registers to other registers internal to processor 100. Reorder/retirement unit 135 includes components, such as the reorder buffers mentioned above, load buffers, and store buffers, to support out-of-order execution and later in-order retirement of instructions executed out-of-order.

Scheduler and execution unit(s) block 140, in one embodiment, includes a scheduler unit to schedule instructions/operation on execution units. For example, a floating point instruction is scheduled on a port of an execution unit that has an available floating point execution unit. Register files associated with the execution units are also included to store information instruction processing results. Exemplary execution units include a floating point execution unit, an integer execution unit, a jump execution unit, a load execution unit, a store execution unit, and other known execution units.

Lower level data cache and data translation buffer (D-TLB) 150 are coupled to execution unit(s) 140. The data cache is to store recently used/operated on elements, such as data operands, which are potentially held in memory coherency states. The D-TLB is to store recent virtual/linear to physical address translations. As a specific example, a processor may include a page table structure to break physical memory into a plurality of virtual pages.

Here, cores 101 and 102 share access to higher-level or further-out cache, such as a second level cache associated with on-chip interface 110. Note that higher-level or further-out refers to cache levels increasing or getting further way from the execution unit(s). In one embodiment, higher-level cache is a last-level data cache—last cache in the memory hierarchy on processor 100—such as a second or third level data cache. However, higher level cache is not so limited, as it may be associated with or include an instruction cache. A trace cache—a type of instruction cache—instead may be coupled after decoder 125 to store recently decoded traces. Here, an instruction potentially refers to a macro-instruction (i.e. a general instruction recognized by the decoders), which may decode into a number of micro-instructions (micro-operations).

In the depicted configuration, processor 100 also includes on-chip interface module 110. Historically, a memory controller, which is described in more detail below, has been included in a computing system external to processor 100. In this scenario, on-chip interface 11 is to communicate with devices external to processor 100, such as system memory 175, a chipset (often including a memory controller hub to connect to memory 175 and an I/O controller hub to connect peripheral devices), a memory controller hub, a northbridge, or other integrated circuit. And in this scenario, bus 105 may include any known interconnect, such as multi-drop bus, a point-to-point interconnect, a serial interconnect, a parallel bus, a coherent (e.g. cache coherent) bus, a layered protocol architecture, a differential bus, and a GTL bus.

Memory 175 may be dedicated to processor 100 or shared with other devices in a system. Common examples of types of memory 175 include DRAM, SRAM, non-volatile memory (NV memory), and other known storage devices. Note that device 180 may include a graphic accelerator, processor or card coupled to a memory controller hub, data storage coupled to an I/O controller hub, a wireless transceiver, a flash device, an audio controller, a network controller, or other known device.

Recently however, as more logic and devices are being integrated on a single die, such as SOC, each of these devices may be incorporated on processor 100. For example in one embodiment, a memory controller hub is on the same package and/or die with processor 100. Here, a portion of the core (an on-core portion) 110 includes one or more controller(s) for interfacing with other devices such as memory 175 or a graphics device 180. The configuration including an interconnect and controllers for interfacing with such devices is often referred to as an on-core (or un-core configuration). As an example, on-chip interface 110 includes a ring interconnect for on-chip communication and a high-speed serial point-to-point link 105 for off-chip communication. Yet, in the SOC environment, even more devices, such as the network interface, co-processors, memory 175, graphics processor 180, and any other known computer devices/interface may be integrated on a single die or integrated circuit to provide small form factor with high functionality and low power consumption.

In one embodiment, processor 100 is capable of executing a compiler, optimization, and/or translator code 177 to compile, translate, and/or optimize application code 176 to support the apparatus and methods described herein or to interface therewith. A compiler often includes a program or set of programs to translate source text/code into target text/code. Usually, compilation of program/application code with a compiler is done in multiple phases and passes to transform hi-level programming language code into low-level machine or assembly language code. Yet, single pass compilers may still be utilized for simple compilation. A compiler may utilize any known compilation techniques and perform any known compiler operations, such as lexical analysis, preprocessing, parsing, semantic analysis, code generation, code transformation, and code optimization.

Larger compilers often include multiple phases, but most often these phases are included within two general phases: (1) a front-end, i.e. generally where syntactic processing, semantic processing, and some transformation/optimization may take place, and (2) a back-end, i.e. generally where analysis, transformations, optimizations, and code generation takes place. Some compilers refer to a middle, which illustrates the blurring of delineation between a front-end and back end of a compiler. As a result, reference to insertion, association, generation, or other operation of a compiler may take place in any of the aforementioned phases or passes, as well as any other known phases or passes of a compiler. As an illustrative example, a compiler potentially inserts operations, calls, functions, etc. in one or more phases of compilation, such as insertion of calls/operations in a front-end phase of compilation and then transformation of the calls/operations into lower-level code during a transformation phase. Note that during dynamic compilation, compiler code or dynamic optimization code may insert such operations/calls, as well as optimize the code for execution during runtime. As a specific illustrative example, binary code (already compiled code) may be dynamically optimized during runtime. Here, the program code may include the dynamic optimization code, the binary code, or a combination thereof.

Similar to a compiler, a translator, such as a binary translator, translates code either statically or dynamically to optimize and/or translate code. Therefore, reference to execution of code, application code, program code, or other software environment may refer to: (1) execution of a compiler program(s), optimization code optimizer, or translator either dynamically or statically, to compile program code, to maintain software structures, to perform other operations, to optimize code, or to translate code; (2) execution of main program code including operations/calls, such as application code that has been optimized/compiled; (3) execution of other program code, such as libraries, associated with the main program code to maintain software structures, to perform other software related operations, or to optimize code; or (4) a combination thereof.

FIG. 2 is a schematic diagram of an example peripheral component interconnect express (PCIe) link architecture 200 in accordance with embodiments of the present disclosure. The PCIe link architecture 200 includes a first component 202, which can be an upstream component, root complex, or switch compliant with the PCIe protocol. The first component 202 can include a downstream port 210 that facilitates communications with downstream components across a link 222, such as a link compliant with the PCIe protocol. The first component 202 can be coupled to a second component 208, which can be a downstream component, endpoint, or switch compliant with the PCIe protocol. In some embodiments, the first component can be linked to one or more intermediate components, such as first retimer 204 and second retimer 206, for example.

In embodiments, the first component 202 can include a downstream port 210 to facilitate downstream communications (e.g., towards the second component 208) with the second component 208 (if directly connected) or with the upstream (pseudo) port 212 of retimer 204. The second component 208 can include an upstream port 220 to facilitate upstream communications (e.g., towards the first component 202) with the first component 202 (if directly connected) or with the downstream (pseudo) port 212 of retimer 204.

In the example shown in FIG. 2, the first component 202 can be linked to a first retimer 204 by a first link segment 224. Likewise, the first retimer 204 can be linked to a second retimer 206 by a link segment 226. The second retimer 206 can be linked to the second component 208 by a link segment 228. Link segments 224, 226, and 228 can make up all or a portion of link 222.

The link 222 can facilitate upstream and downstream communications between the first component 202 and the second component 208. In embodiments, upstream communications refers to data and control information transmitted from the second component 208 towards the first component 202; and downstream communications refers to data and control information transmitted from the first component 202 towards the second component 208. As mentioned above, one or more retimers (e.g., retimers 204 and 206) can be used to extend the range of the link 222 between the first component 202 and the second component 208.

A link 222 incorporating one or more retimers (e.g., retimers 204, 206) can form two or more separate electrical sub-links at data rates comparable to data rates realized by links employing similar protocols but with no retimers. For instance, if link 222 included a single retimer, the link 222 could form a link with two separate sub-links, each operating at 8.0 GT/s or higher. As shown in FIG. 2, multiple retimers 204, 206 can be utilized to extend link 222. Three link segments 222, 224, and 226 can be defined through the two retimers 204, 206, with a first sublink 222 connecting the first component 202 to the first retimer 204, a second sublink 224 connecting the first retimer 204 to the second retimer 206, and the third sublink 226 connecting the second retimer 206 to the second component 208.

As shown in the example FIG. 2, in some implementations, a retimer can include two ports (or pseudo ports), and the ports can determine their respective downstream/upstream orientation dynamically. In embodiments, retimer 204 can include an upstream port 212 and a downstream port 214. Likewise, retimer 206 can include an upstream port 216 and a downstream port 218. Each retimer 204, 206 can have an upstream path and a downstream path. Further, retimers 204, 206 can support operating modes including a forwarding mode and an executing mode. A retimer 204, 206 in some instances can decode data received on the sub-link and re-encode the data that it is to forward downstream on its other sublink. As such, retimers may capture the received bit stream prior to regenerating and re-transmitting the bit stream to another device or even another retimer (or redriver or repeater). In some cases, the retimer can modify some values in the data it receives, such as when processing and forwarding ordered set data. Additionally, a retimer can potentially support any width option as its maximum width, such as a set of width options defined by a specification such as PCIe.

As data rates of serial interconnects (e.g., PCIe, UPI, USB, etc.) increase, retimers are increasingly used to extend the channel reach. Multiple retimers can be cascaded for even longer channel reach. It is expected that as signal speeds increase, channel reach will typically decrease as a general matter. Accordingly, as interconnect technologies accelerate, the use of retimers may become more common. As an example, as PCIe Gen-4, with its 16 GT/s, is adopted in favor of PCIe Gen-3 (8 GT/s), the use of retimers in PCIe interconnects may increase, as may be the case in other interconnects as speeds increase.

The downstream port 210 (e.g., in the first component 202, which can be an upstream component, such as a Root Complex or switch) is accessible to system software prior to link establishment or when the link 222 is unable to function properly. In embodiments, registers, such as the link capability registers, can be set to perform clock mode selection in the downstream port 210. System firmware/software can configure the downstream port 210 into the expected mode, and if a change is needed that this will be done by system firmware/software, rather than by hardware.

PCIe supports hot plug (also known as hot swap) functionality, but can lack a consistent way to report certain key bits of information to system software, making it difficult for PCIe subsystems to be managed optimally, and leading to system limitations and poor user experiences. These same limitations affect Converged Input/Output (CIO) or “open” Thunderbolt because these I/O configurations use PCIe as a tunneled I/O architecture.

Hot plugging is a term that refers to the ability to add components to a host system that would expand the host system without significant interruption to the system. Hot swapping can be defined as replacing or adding components without stopping or shutting down the host system. In this disclosure, the terms are used synonymously.

With the appropriate hot plug-functionality software installed on the host system, a user can plug and unplug hot plug-capable components into a hot plug-capable downstream port without rebooting the host system. Examples of this hot plug functionality include the Universal Serial Bus (USB), PCIe, and CIO protocols, each of which can allow a user to add or remove peripheral components such as a monitor, storage device, mouse, keyboard, printer, portable hard drive, or other peripheral device.

PCIe defines a “Designated Vendor Specific Extended Capability” (DVSEC), which is an extended capability that can be used by a vendor to define a configuration register structure that can be implemented by silicon vendors, while providing a consistent hardware/software interface. This disclosure can use DVSEC in embodiments to overcome the reporting deficiencies described above. The PCIe DVSEC is an extended capability that is permitted to be implemented by any PCIe function. This allows PCIe component vendors to use the extended capability mechanism to expose vendor-specific registers that can be present in components by a variety of vendors.

The DVSEC capabilities being defined herein are applicable for any PCIe subsystem. Most of the examples and software implementation notes in this document are provided in the context of CIO, but are not limited to CIO. CIO is being used herein as an example architecture.

CIO is a tunnel for PCIe and DisplayPort. A CIO link can be of a single lane or two lanes aggregated, running at 10 Gbps to 40 Gbps, or beyond. CIO can operate across a USB Type-C connector (as an alternate mode) and enables PCIe devices outside of the system box. Daisy chain topologies with up to 6 CIO devices are supported.

CIO peripherals are particularly problematic because CIO peripherals appear as a large set of PCIe bridges and end points to system software. System software may be unable to differentiate between internal PCI devices (that have unchanging resource needs) and externally connected devices (that may have changing resource needs), which prevents optimal resource allocation. In particular, system software is unable to predict bus numbers and levels of resources to reserve for a hot plug capable downstream port within a CIO hierarchy. System software is also unable to determine other attributes of the hierarchy, such as D3Cold support, or the requirement for a managed device removal. Lack of this information can result in inefficient device enumeration and management, leading to a poor user experience or loss of functionality.

Aspects of the present disclosure facilitates more precise information concerning resources and/or bus number used by a hot plug-capable device, such as a device internal to the root complex or a downstream device (e.g., an externally connected device connected to a downstream port of a host device), as opposed to guessing or estimating the resources and/or bus numbers required. As result, corner cases can develop where either the reservation is not large enough or too large resulting in wastage. Aspects of the embodiments facilitate D3Cold support without using additional BIOS functionality that can be unavailable for hot plug devices. Aspects of the embodiments also facilitate indications of general attributes, such as port type, which can be vendor-specific capabilities.

This disclosure describes definitions and implementations of PCIe Designated Vendor specific Extended Capability (DVSEC) capabilities that can be indicated to and processed by host root ports and downstream ports of CIO/PCIe peripherals or other devices that will provide resource requirements and attribute information to system software.

System software, such as that which manages host root ports and/or downstream ports for connected devices, can parse the DVSEC to determine resource requirements allowing for successful enumeration of hot plugged devices and keeping resource wastage to a minimum (including bus/device/function (BDF) and memory-mapped input/output (MMIO)). Other information within the DVSEC indicates conforming to requirements for robust D3Cold support, a “Safe Eject” hint and, device/host router differentiation allow efficient device management.

Aspects of the embodiments can facilitate system software to apply differential policies for security, resource allocation, power management, etc. by identifying a downstream component or hierarchy of downstream components (e.g., a daisy-chained hierarchy of downstream components) as a CIO or hot plug device(s). In embodiments, a Port Type field in DVSEC capabilities definition will allow system software to identify CIO ports.

To support full daisy chain functionality, system software would have to pre-allocate enough bus numbers and resources (such as MMIO). Pre-allocation would have to be precise such that there is no wastage (especially for BDFs) and just enough such that devices getting hot plugged enumerate successfully without failures or resource rebalances (both of which lead loss of functionality). DVSEC can provide hints in a DVSEC capabilities definition to allow the system software to determine if a hot plug capable port is expandable or not and indicate the number of buses that need to be reserved.

Additional hints in the DVSEC capabilities definition can allow system software to efficiently enumerate and manage the hierarchy below the port. Such additional hints can include a hint that allows the system software to differentiate between host and device router. This distinction allows system software to differentially apply polices (e.g. for Security). Other hints can include a hint that allows the system software to determine a need for “managed” removal of device allowing for better user notification (e.g., safe unplug notifications); and/or a hint that allows system software to cause a bridge to support D3Cold that helps system software to determine that when the corresponding power resource is turned off, the corresponding port is able to transition/wake back to D0.

FIG. 3 is a schematic block diagram of a connected system 300 that includes a hierarchy of device connected to a host by a PCIe-compliant link in accordance to embodiments of the present disclosure. The system 300 can include a host 350 that is connected by a PCIe-compliant link (such as a CIO) to one or more connected downstream components, such as device 1 360 and device 3 390. The system 300 can also include one or more daisy-chained downstream components, such as device 2 370, which is connected to the host via device 1 360 (e.g., by a daisy-chain type of connection). Other daisy-chain connected downstream components can be included, which are represented by device (n) 380.

Each device of system 300 can include a plurality of ports, as discussed above with FIG. 2. For example, the host can include a root port 302, which can be part of a root complex that includes a plurality of switches and switch ports. The root port 302 can include an upstream port 304 that is connected to one or more downstream ports 306-312 to facilitate transmission and reception of data and control signals with downstream components, such as devices 1-n. For example, device 1 360 can be connected to the root port 302 by an upstream port 316 connected to the downstream port 308 of the host 350. Likewise, device 3 390 can be connected to the host 350 by a downstream port 312 connected to an upstream port 336.

One or more downstream ports can be hot plug capable to facilitate hot plug detection of connected devices, and in some embodiments, to facilitate daisy-chaining of downstream components. For example, downstream port 308 can be a hot plug capable downstream port that also facilitates daisy chaining of other downstream devices. For example, device 2 370 can be connected to the root port 302 by an upstream port 324 connected to an expandable hot plug capable downstream port 322 associated with device 1 360. Another downstream port 318 can be a non-expandable downstream port that is connected to a device 320. Device 2 370 can include an upstream port 324 connected to downstream port 322. Device 2 can include a downstream port 326 connected to a device 328 (e.g., a non-expandable downstream port that is connected to an endpoint device). Device 2 can also include a downstream port 330 that is hot plug capable and connected to an upstream port 332 of device (n) 380. Device (n) 380 represents other daisy chained downstream components connected to the root port 302 by an expandable hot plug capable downstream port 330 associated with device 2 370.

Likewise downstream port 312 can be a hot plug capable downstream port that is connected to device 3 390 by an upstream port 336. Device 3 can include a downstream port 338 and a hot plug-capable downstream port 342.

Downstream devices shown in FIG. 3 can include any peripheral or other type of device connected to the host 350 across a PCIe-compliant link, such as those that use CIO or Thunderbolt type connection protocols. One or more of devices 1, 2, 3, or n (360, 370, 390, or 380, respectively) can utilize the DVSEC capability definition described herein to inform the host 350 of certain extended capabilities to allow the host 350 to configure certain attributes for the respective device(s) upon detection of the hot plug detection.

FIG. 4 is a schematic diagram of a DVSEC capabilities definition 400 that includes one or more attribute hint bits in accordance with embodiments of the present disclosure. As described above, the DVSEC capabilities definition 400 can include one or more indicators or hints represented at as register bits that can inform a host device about how to configure or apply certain attributes when the host device detects a connection (e.g., a hot plug connection) of a downstream device. The DVSEC definition 400 can be communicated to the host device, which can use system software configure the resources or other attributes indicated by the DVSEC definition.

In a first example, the DVSEC definition 400 can include a bus number reservation hint 402. The bus number hint reservation can indicate to the system software of the host device to determine a number of buses to reserve for the hierarchy underneath the root port or intermediate switch downstream ports (e.g., in a daisy chained hierarchy). The bus number reservation hint 402 can be defined as follows:

Bus number reservation hint (Offset = 0x0C, Size = 1 byte) Bit Attri- Location Description and Software Implementation Note butes 7:0 or 0x00: Not implemented RO 23:16 0x01-0xFE: Number of buses required 0xFF: Unknown This field is applicable to root ports or switch downstream ports. This hint allows system software to determine number of buses to reserve for the hierarchy underneath. Bus reservation allows system software to successfully support enumera- tion of long daisy chains without running out of bus numbers.

The system software of the host device can set a number of buses for the connected device based on the bus number reservation hint 402 in the DVSEC definition 400. Though indicated as having bit location 7:0 or 23:16, other bit locations can be used in the DVSEC definition 400, depending on the implantation choice.

In a second example, the DVSEC definition 400 can include a port type indicator 404. The port type indicator 404 can be used to identify the port type of the connected device to system software. System software can use this field to differentially apply software polices based on the indicated port type. The port type indicator 404 can be defined as follows:

Port Type (Offset = 0x0C, Size = 4 bits) Bit Attri- Location Description and Software Implementation Note butes 9:6 or 0x00: Unknown RO 15:8 0x01: CIO 0x02-0xFF: RESERVED for future use The port type indicator can be used to identify the port type of the connected device to system software. System software can use this field to differentially apply software polices based on the indicated port type.

The system software of the host device can set policies for the connected device based, at least in part, on the port type indicated by the port type indicator 404 in the DVSEC definition 400. Though indicated as having bit location 9:6 or 15:8, other bit locations can be used in the DVSEC definition 400, depending on the implantation choice.

In another example, the DVSEC definition 400 can include a D3Cold support indicator 406. The D3Cold support indicator 406 is applicable to root ports or switch downstream ports. The D3Cold support indicator includes a bit that is set when it is indicated that, when the corresponding power resource's is/are turned off, the port and attached device(s) are able to transition/wake back to D0 (fully on) state without issues, including in hot plug cases. The D3Cold state is one of two D3 (low power) sub-states, the other being D3Hot state.

The D3Cold support indicator 406 can be defined as follows:

D3Cold support (Offset = 0x0C, size = 1 bit) Bit Attri- Location Description and Software Implementation Note butes 4 or 5 0: Not implemented RO 1: D3Cold supported This field is applicable to root ports or switch downstream ports. This bit must only be set when it is guaranteed that, when the corresponding power resource/s is/are turned off, the port and attached device(s) are able to transition/wake back to D0 without issues, including in hot plug cases. It is expected that downstream ports indicating support for D3cold implement mechanisms to control the power delivered to the attached devices, for example through a wire or control bus (such as I2C/ SMbus or I3C) to a power FET, however the specifics of how this mechanism is operated are not covered by this document. System software can use this informa- tion to qualify the use of run-time power management, e.g. where a hierarchy below a specific port is placed into D3cold. In some cases system software may be able to “roll up” the information provided here to enable (/disable) D3cold to a larger hierarchy, e.g. at an expandable port that includes multiple non-expandable ports below switches. In such uses, system software must ensure that D3Cold support is advertised by *all* devices and bridges below the control point at which it is considering entering into D3cold.

The system software of the host device use the D3Cold support indicator 406 to implement power management mechanisms for the connected device, and in some cases for a hierarchy of connected devices. Though indicated as having bit location 4 or 5, other bit locations can be used in the DVSEC definition 400, depending on the implantation choice.

In another example, the DVSEC definition 400 can include a host router indication 408. The host router indication 408 is applicable to root ports or switch downstream ports on a host platform. The host router indication 408 allows system software to determine if the port of the connected device is part of host router. This distinction allows system software to differentially apply polices (e.g. for security). Though indicated as using bit locations 3:2 or 4, other bit locations in the DVSEC definition 400 could be used, depending on implementation choice. The host router indication 408 can be defined as follows:

Host Indication (Offset = 0x0C, Size = 2 bits) Bit Attri- Location Description and Software Implementation Note butes 3:2 or 4 00: Not implemented (not a host) RO 01: Host - Indicates a port that is physically a part of the host system 10: Reserved 11: Host External-Facing - Indicates a port that is an external-facing port, accessible to users, of a host system This field is applicable to root ports or switch down- stream ports on host platform. This indication allows system software to determine if this port is part of host router. This distinction allows system software to differentially apply polices (e.g. for Security). Host External-Facing ports represent the physical boundary of a host system. It is not permitted to indicate that a port is “01” or “11” downstream of a port that is indicated “11”, and system soft- ware is recommended to quarantine any such hardware detected. .

In another example, the DVSEC definition 400 can include a safe eject hint 410. The safe eject hint 410 is applicable to switch downstream ports and provides hints to system software to allow system software to determine if the PCIe end point connected to this port requires managed removal (e.g., a user may use a soft eject prior to physically removing the device from the port). The safe eject hint 410 can be defined as follows:

Safe Eject Hint (Offset = 0x0C, Size = 1 bit) Bit Attri- Location Description and Software Implementation Note butes 2 or 5 0: Not implemented RO 1: Safe eject requested This field is applicable only to switch down- stream ports and provides hints to system software to determine if the PCIe end point connected to this port requires managed removal. System software can use this hint to notify user and populate the safe eject menu with device details. This however does not exclude the system software from the need to robustly handle surprise remove events.

System software can use the safe eject hint 410 to notify a user that a safe ejection is preferred prior to removing a device, and populate the safe eject menu with device details. Though indicated as having bit location 2 or 5, other bit locations can be used for the safe eject hint 410 in the DVSEC definition 400.

In another example, the DVSEC definition 400 can include a port expandability indicator 412. The port expandability indicator 412 is applicable to root ports or switch downstream ports. The port expandability indicator 412 provides indicates to system software if this port is expandable. An example of an expandable root port are CIO ports on the host or daisy chain capable ports on CIO peripherals. An example of a non-expandable port is a PCIe port permanently attached to a specific PCIe Device, or a Port where it is possible to determine the full resource requirements at the time of initial enumeration including for scenarios where a fixed resource requirement is pre-allocated, e.g. for a memory card reader. This information allows the operating system to appropriately reserve resources such as MMIO based on the port type. For example, a non-expandable port can be allocated enough resources for only the PCIe device discovered at enumeration, whereas an expandable port can be allocated a larger set resources to accommodate future additional resource needs.

The port expandability indicator 412 can be defined as follows:

Port Expandability (Offset = 0x0C, Size = 2 bit) Bit Attri- Location Description and Software Implementation Note butes 1:0 00: Not implemented RO 01: Non-Expandable port with fixed resource requirements 10: Expandable (or daisy chain capable) port with resource requirements that can change at run time 11: Reserved This field is applicable to root ports or switch downstream ports. This field provides indicates to system software if this port is expandable. An example of an expandable root port are CIO ports on the host or daisy chain capable ports on CIO peripherals. An example of a non-expand- able port is a PCIe Port permanently attached to a specific PCIe Device, or a Port where it is possible to determine the full resource requirements at the time of initial enumeration including for scenarios where a fixed resource requirement is pre-allocated, e.g. for a memory card reader. This information allows the operat- ing system to appropriately reserve resources such as MMIO based on the port type. For example, a non-expandable port can be allocated enough resources for only the PCIe device discovered at enumeration, whereas an expandable port can be allocated a larger set resources to accommodate future additional resource needs.

The port expandability indicator 412 allows the operating system (or system software, more generally) to appropriately reserve resources, such as MMIO, based on the port type. For example, a non-expandable port can be allocated sufficient resources for the PCIe device discovered at enumeration, whereas an expandable port can be allocated a larger set resources to accommodate future additional resource needs. Though indicated as having bit location 1:0, other bit locations can be used in the DVSEC definition 400 depending on implementation choice.

FIG. 5 is a process flow diagram 500 for a host device to implement one or more attributes of a downstream component based on a DVSEC capabilities definition in accordance with embodiments of the present disclosure. At the outset, system software (on a host device or a switch downstream port) can detect the connection of a downstream component, such as a peripheral device or other type of downstream device (502). The detection of the connection can include a hot plug detection of a device connected to a hot plug-capable downstream port. Upon detection of the device, the system software can receive DVSEC capabilities definition information from the connected device (504). The system software can read one or more DVSEC capability indicators from the capabilities definition information that informs the system software about one or more configuration parameters or attributes for the connected downstream device (506). The system software can use the DVSEC capability indicator(s) to configure one or more operational parameters for the downstream component, such as the number of buses, the port type, the expandability capability, the D3Cold support status, the host router indicator, and/or the safe eject requirements of the downstream component. The system software can then coordinate data and control signal communications between the host device and the connected downstream device based on the applied configuration parameters and attributes (508).

One interconnect fabric architecture includes the Peripheral Component Interconnect (PCI) Express (PCIe) architecture. A primary goal of PCIe is to enable components and devices from different vendors to inter-operate in an open architecture, spanning multiple market segments; Clients (Desktops and Mobile), Servers (Standard and Enterprise), and Embedded and Communication devices. PCI Express is a high performance, general purpose I/O interconnect defined for a wide variety of future computing and communication platforms. Some PCI attributes, such as its usage model, load-store architecture, and software interfaces, have been maintained through its revisions, whereas previous parallel bus implementations have been replaced by a highly scalable, fully serial interface. The more recent versions of PCI Express take advantage of advances in point-to-point interconnects, Switch-based technology, and packetized protocol to deliver new levels of performance and features. Power Management, Quality Of Service (QoS), Hot-Plug/Hot-Swap support, Data Integrity, and Error Handling are among some of the advanced features supported by PCI Express.

Referring to FIG. 6, an embodiment of a fabric composed of point-to-point Links that interconnect a set of components is illustrated. System 600 includes processor 605 and system memory 610 coupled to controller hub 615. Processor 605 includes any processing element, such as a microprocessor, a host processor, an embedded processor, a co-processor, or other processor. Processor 605 is coupled to controller hub 615 through front-side bus (FSB) 606. In one embodiment, FSB 606 is a serial point-to-point interconnect as described below. In another embodiment, link 606 includes a serial, differential interconnect architecture that is compliant with different interconnect standard.

System memory 610 includes any memory device, such as random access memory (RAM), non-volatile (NV) memory, or other memory accessible by devices in system 600. System memory 610 is coupled to controller hub 615 through memory interface 616. Examples of a memory interface include a double-data rate (DDR) memory interface, a dual-channel DDR memory interface, and a dynamic RAM (DRAM) memory interface.

In one embodiment, controller hub 615 is a root hub, root complex, or root controller in a Peripheral Component Interconnect Express (PCIe or PCIE) interconnection hierarchy. Examples of controller hub 615 include a chipset, a memory controller hub (MCH), a northbridge, an interconnect controller hub (ICH) a southbridge, and a root port controller/hub. Often the term chipset refers to two physically separate controller hubs, i.e. a memory controller hub (MCH) coupled to an interconnect controller hub (ICH). Note that current systems often include the MCH integrated with processor 605, while controller 615 is to communicate with I/O devices, in a similar manner as described below. In some embodiments, peer-to-peer routing is optionally supported through root complex 615.

Here, controller hub 615 is coupled to switch/bridge 620 through serial link 619. Input/output modules 617 and 621, which may also be referred to as interfaces/ports 617 and 621, include/implement a layered protocol stack to provide communication between controller hub 615 and switch 620. In one embodiment, multiple devices are capable of being coupled to switch 620.

Switch/bridge 620 routes packets/messages from device 625 upstream, i.e. up a hierarchy towards a root complex, to controller hub 615 and downstream, i.e. down a hierarchy away from a root port controller, from processor 605 or system memory 610 to device 625. Switch 620, in one embodiment, is referred to as a logical assembly of multiple virtual PCI-to-PCI bridge devices. Device 625 includes any internal or external device or component to be coupled to an electronic system, such as an I/O device, a Network Interface Controller (NIC), an add-in card, an audio processor, a network processor, a hard-drive, a storage device, a CD/DVD ROM, a monitor, a printer, a mouse, a keyboard, a router, a portable storage device, a Firewire device, a Universal Serial Bus (USB) device, a scanner, and other input/output devices. Often in the PCIe vernacular, such as device, is referred to as an endpoint. Although not specifically shown, device 625 may include a PCIe to PCI/PCI-X bridge to support legacy or other version PCI devices. Endpoint devices in PCIe are often classified as legacy, PCIe, or root complex integrated endpoints.

Graphics accelerator 630 is also coupled to controller hub 615 through serial link 632. In one embodiment, graphics accelerator 630 is coupled to an MCH, which is coupled to an ICH. Switch 620, and accordingly I/O device 625, is then coupled to the ICH. I/O modules 631 and 618 are also to implement a layered protocol stack to communicate between graphics accelerator 630 and controller hub 615. Similar to the MCH discussion above, a graphics controller or the graphics accelerator 630 itself may be integrated in processor 605.

Turning to FIG. 7 an embodiment of a layered protocol stack is illustrated. Layered protocol stack 700 includes any form of a layered communication stack, such as a Quick Path Interconnect (QPI) stack, a PCie stack, a next generation high performance computing interconnect stack, or other layered stack. Although the discussion immediately below in reference to FIGS. 6-9 are in relation to a PCIe stack, the same concepts may be applied to other interconnect stacks. In one embodiment, protocol stack 700 is a PCIe protocol stack including transaction layer 705, link layer 710, and physical layer 720. An interface, such as interfaces 617, 618, 621, 622, 626, and 631 in FIG. 1, may be represented as communication protocol stack 700. Representation as a communication protocol stack may also be referred to as a module or interface implementing/including a protocol stack.

PCI Express uses packets to communicate information between components. Packets are formed in the Transaction Layer 705 and Data Link Layer 710 to carry the information from the transmitting component to the receiving component. As the transmitted packets flow through the other layers, they are extended with additional information necessary to handle packets at those layers. At the receiving side the reverse process occurs and packets get transformed from their Physical Layer 720 representation to the Data Link Layer 710 representation and finally (for Transaction Layer Packets) to the form that can be processed by the Transaction Layer 705 of the receiving device.

Transaction Layer

In one embodiment, transaction layer 705 is to provide an interface between a device's processing core and the interconnect architecture, such as data link layer 710 and physical layer 720. In this regard, a primary responsibility of the transaction layer 705 is the assembly and disassembly of packets (i.e., transaction layer packets, or TLPs). The translation layer 705 typically manages credit-base flow control for TLPs. PCIe implements split transactions, i.e. transactions with request and response separated by time, allowing a link to carry other traffic while the target device gathers data for the response.

In addition PCIe utilizes credit-based flow control. In this scheme, a device advertises an initial amount of credit for each of the receive buffers in Transaction Layer 705. An external device at the opposite end of the link, such as controller hub 115 in FIG. 1, counts the number of credits consumed by each TLP. A transaction may be transmitted if the transaction does not exceed a credit limit. Upon receiving a response an amount of credit is restored. An advantage of a credit scheme is that the latency of credit return does not affect performance, provided that the credit limit is not encountered.

In one embodiment, four transaction address spaces include a configuration address space, a memory address space, an input/output address space, and a message address space. Memory space transactions include one or more of read requests and write requests to transfer data to/from a memory-mapped location. In one embodiment, memory space transactions are capable of using two different address formats, e.g., a short address format, such as a 32-bit address, or a long address format, such as 64-bit address. Configuration space transactions are used to access configuration space of the PCIe devices. Transactions to the configuration space include read requests and write requests. Message space transactions (or, simply messages) are defined to support in-band communication between PCIe agents.

Therefore, in one embodiment, transaction layer 705 assembles packet header/payload 706. Format for current packet headers/payloads may be found in the PCIe specification at the PCIe specification website.

Quickly referring to FIG. 8, an embodiment of a PCIe transaction descriptor is illustrated. In one embodiment, transaction descriptor 800 is a mechanism for carrying transaction information. In this regard, transaction descriptor 800 supports identification of transactions in a system. Other potential uses include tracking modifications of default transaction ordering and association of transaction with channels.

Transaction descriptor 800 includes global identifier field 802, attributes field 804 and channel identifier field 806. In the illustrated example, global identifier field 802 is depicted comprising local transaction identifier field 808 and source identifier field 810. In one embodiment, global transaction identifier 802 is unique for all outstanding requests.

According to one implementation, local transaction identifier field 808 is a field generated by a requesting agent, and it is unique for all outstanding requests that require a completion for that requesting agent. Furthermore, in this example, source identifier 810 uniquely identifies the requestor agent within a PCIe hierarchy. Accordingly, together with source ID 810, local transaction identifier 808 field provides global identification of a transaction within a hierarchy domain.

Attributes field 804 specifies characteristics and relationships of the transaction. In this regard, attributes field 804 is potentially used to provide additional information that allows modification of the default handling of transactions. In one embodiment, attributes field 804 includes priority field 812, reserved field 814, ordering field 816, and no-snoop field 818. Here, priority sub-field 812 may be modified by an initiator to assign a priority to the transaction. Reserved attribute field 814 is left reserved for future, or vendor-defined usage. Possible usage models using priority or security attributes may be implemented using the reserved attribute field.

In this example, ordering attribute field 816 is used to supply optional information conveying the type of ordering that may modify default ordering rules. According to one example implementation, an ordering attribute of “0” denotes default ordering rules are to apply, wherein an ordering attribute of “1” denotes relaxed ordering, wherein writes can pass writes in the same direction, and read completions can pass writes in the same direction. Snoop attribute field 818 is utilized to determine if transactions are snooped. As shown, channel ID Field 806 identifies a channel that a transaction is associated with.

Link Layer

Link layer 710, also referred to as data link layer 710, acts as an intermediate stage between transaction layer 705 and the physical layer 720. In one embodiment, a responsibility of the data link layer 710 is providing a reliable mechanism for exchanging Transaction Layer Packets (TLPs) between two components a link. One side of the Data Link Layer 710 accepts TLPs assembled by the Transaction Layer 705, applies packet sequence identifier 711, i.e. an identification number or packet number, calculates and applies an error detection code, i.e. CRC 712, and submits the modified TLPs to the Physical Layer 720 for transmission across a physical to an external device.

Physical Layer

In one embodiment, physical layer 720 includes logical sub block 721 and electrical sub-block 722 to physically transmit a packet to an external device. Here, logical sub-block 721 is responsible for the “digital” functions of Physical Layer 721. In this regard, the logical sub-block includes a transmit section to prepare outgoing information for transmission by physical sub-block 722, and a receiver section to identify and prepare received information before passing it to the Link Layer 710.

Physical block 722 includes a transmitter and a receiver. The transmitter is supplied by logical sub-block 721 with symbols, which the transmitter serializes and transmits onto to an external device. The receiver is supplied with serialized symbols from an external device and transforms the received signals into a bit-stream. The bit-stream is de-serialized and supplied to logical sub-block 721. In one embodiment, an 8b/10b transmission code is employed, where ten-bit symbols are transmitted/received. Here, special symbols are used to frame a packet with frames 723. In addition, in one example, the receiver also provides a symbol clock recovered from the incoming serial stream.

As stated above, although transaction layer 705, link layer 710, and physical layer 720 are discussed in reference to a specific embodiment of a PCIe protocol stack, a layered protocol stack is not so limited. In fact, any layered protocol may be included/implemented. As an example, an port/interface that is represented as a layered protocol includes: (1) a first layer to assemble packets, i.e. a transaction layer; a second layer to sequence packets, i.e. a link layer; and a third layer to transmit the packets, i.e. a physical layer. As a specific example, a common standard interface (CSI) layered protocol is utilized.

Referring next to FIG. 9, an embodiment of a PCIe serial point to point fabric is illustrated. Although an embodiment of a PCIe serial point-to-point link is illustrated, a serial point-to-point link is not so limited, as it includes any transmission path for transmitting serial data. In the embodiment shown, a basic PCIe link includes two, low-voltage, differentially driven signal pairs: a transmit pair 906/911 and a receive pair 912/907. Accordingly, device 905 includes transmission logic 906 to transmit data to device 910 and receiving logic 907 to receive data from device 910. In other words, two transmitting paths, i.e. paths 916 and 917, and two receiving paths, i.e. paths 918 and 919, are included in a PCIe link.

A transmission path refers to any path for transmitting data, such as a transmission line, a copper line, an optical line, a wireless communication channel, an infrared communication link, or other communication path. A connection between two devices, such as device 905 and device 910, is referred to as a link, such as link 415. A link may support one lane—each lane representing a set of differential signal pairs (one pair for transmission, one pair for reception). To scale bandwidth, a link may aggregate multiple lanes denoted by xN, where N is any supported Link width, such as 1, 2, 4, 8, 12, 16, 32, 64, or wider.

A differential pair refers to two transmission paths, such as lines 416 and 417, to transmit differential signals. As an example, when line 416 toggles from a low voltage level to a high voltage level, i.e. a rising edge, line 417 drives from a high logic level to a low logic level, i.e. a falling edge. Differential signals potentially demonstrate better electrical characteristics, such as better signal integrity, i.e. cross-coupling, voltage overshoot/undershoot, ringing, etc. This allows for better timing window, which enables faster transmission frequencies.

Note that the apparatus, methods, and systems described above may be implemented in any electronic device or system as aforementioned. As specific illustrations, the figures below provide exemplary systems for utilizing the invention as described herein. As the systems below are described in more detail, a number of different interconnects are disclosed, described, and revisited from the discussion above. And as is readily apparent, the advances described above may be applied to any of those interconnects, fabrics, or architectures.

Turning to FIG. 10, a block diagram of an exemplary computer system formed with a processor that includes execution units to execute an instruction, where one or more of the interconnects implement one or more features in accordance with one embodiment of the present invention is illustrated. System 1000 includes a component, such as a processor 1002 to employ execution units including logic to perform algorithms for process data, in accordance with the present invention, such as in the embodiment described herein. System 1000 is representative of processing systems based on the PENTIUM III™, PENTIUM 4™, Xeon™, Itanium, XScale™ and/or StrongARM™ microprocessors available from Intel Corporation of Santa Clara, Calif., although other systems (including PCs having other microprocessors, engineering workstations, set-top boxes and the like) may also be used. In one embodiment, sample system 1000 executes a version of the WINDOWS™ operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (UNIX and Linux for example), embedded software, and/or graphical user interfaces, may also be used. Thus, embodiments of the present invention are not limited to any specific combination of hardware circuitry and software.

Embodiments are not limited to computer systems. Alternative embodiments of the present invention can be used in other devices such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol devices, digital cameras, personal digital assistants (PDAs), and handheld PCs. Embedded applications can include a micro controller, a digital signal processor (DSP), system on a chip, network computers (NetPC), set-top boxes, network hubs, wide area network (WAN) switches, or any other system that can perform one or more instructions in accordance with at least one embodiment.

In this illustrated embodiment, processor 1002 includes one or more execution units 1008 to implement an algorithm that is to perform at least one instruction. One embodiment may be described in the context of a single processor desktop or server system, but alternative embodiments may be included in a multiprocessor system. System 1000 is an example of a ‘hub’ system architecture. The computer system 1000 includes a processor 1002 to process data signals. The processor 1002, as one illustrative example, includes a complex instruction set computer (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor implementing a combination of instruction sets, or any other processor device, such as a digital signal processor, for example. The processor 1002 is coupled to a processor bus 1010 that transmits data signals between the processor 1002 and other components in the system 1000. The elements of system 1000 (e.g. graphics accelerator 1012, memory controller hub 1016, memory 1020, I/O controller hub 1024, wireless transceiver 1026, Flash BIOS 1028, Network controller 1034, Audio controller 1036, Serial expansion port 1038, I/O controller 1040, etc.) perform their conventional functions that are well known to those familiar with the art.

In one embodiment, the processor 1002 includes a Level 1 (L1) internal cache memory 1004. Depending on the architecture, the processor 1002 may have a single internal cache or multiple levels of internal caches. Other embodiments include a combination of both internal and external caches depending on the particular implementation and needs. Register file 1006 is to store different types of data in various registers including integer registers, floating point registers, vector registers, banked registers, shadow registers, checkpoint registers, status registers, and instruction pointer register.

Execution unit 1008, including logic to perform integer and floating point operations, also resides in the processor 1002. The processor 1002, in one embodiment, includes a microcode (ucode) ROM to store microcode, which when executed, is to perform algorithms for certain macroinstructions or handle complex scenarios. Here, microcode is potentially updateable to handle logic bugs/fixes for processor 1002. For one embodiment, execution unit 1008 includes logic to handle a packed instruction set 1009. By including the packed instruction set 1009 in the instruction set of a general-purpose processor 1002, along with associated circuitry to execute the instructions, the operations used by many multimedia applications may be performed using packed data in a general-purpose processor 1002. Thus, many multimedia applications are accelerated and executed more efficiently by using the full width of a processor's data bus for performing operations on packed data. This potentially eliminates the need to transfer smaller units of data across the processor's data bus to perform one or more operations, one data element at a time.

Alternate embodiments of an execution unit 1008 may also be used in micro controllers, embedded processors, graphics devices, DSPs, and other types of logic circuits. System 1000 includes a memory 1020. Memory 1020 includes a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory device, or other memory device. Memory 1020 stores instructions and/or data represented by data signals that are to be executed by the processor 1002.

Note that any of the aforementioned features or aspects of the invention may be utilized on one or more interconnect illustrated in FIG. 10. For example, an on-die interconnect (ODI), which is not shown, for coupling internal units of processor 1002 implements one or more aspects of the invention described above. Or the invention is associated with a processor bus 1010 (e.g. Intel Quick Path Interconnect (QPI) or other known high performance computing interconnect), a high bandwidth memory path 1018 to memory 1020, a point-to-point link to graphics accelerator 1012 (e.g. a Peripheral Component Interconnect express (PCIe) compliant fabric), a controller hub interconnect 1022, an I/O or other interconnect (e.g. USB, PCI, PCIe) for coupling the other illustrated components. Some examples of such components include the audio controller 1036, firmware hub (flash BIOS) 1028, wireless transceiver 1026, data storage 1024, legacy I/O controller 1010 containing user input and keyboard interfaces 1042, a serial expansion port 1038 such as Universal Serial Bus (USB), and a network controller 1034. The data storage device 1024 can comprise a hard disk drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

Referring now to FIG. 11, shown is a block diagram of a second system 1100 in accordance with an embodiment of the present invention. As shown in FIG. 11, multiprocessor system 1100 is a point-to-point interconnect system, and includes a first processor 1170 and a second processor 1180 coupled via a point-to-point interconnect 1150. Each of processors 1170 and 1180 may be some version of a processor. In one embodiment, 1152 and 1154 are part of a serial, point-to-point coherent interconnect fabric, such as Intel's Quick Path Interconnect (QPI) architecture. As a result, the invention may be implemented within the QPI architecture.

While shown with only two processors 1170, 1180, it is to be understood that the scope of the present invention is not so limited. In other embodiments, one or more additional processors may be present in a given processor.

Processors 1170 and 1180 are shown including integrated memory controller units 1172 and 1182, respectively. Processor 1170 also includes as part of its bus controller units point-to-point (P-P) interfaces 1176 and 1178; similarly, second processor 1180 includes P-P interfaces 1186 and 1188. Processors 1170, 1180 may exchange information via a point-to-point (P-P) interface 1150 using P-P interface circuits 1178, 1188. As shown in FIG. 11, IMCs 1172 and 1182 couple the processors to respective memories, namely a memory 1132 and a memory 1134, which may be portions of main memory locally attached to the respective processors.

Processors 1170, 1180 each exchange information with a chipset 1190 via individual P-P interfaces 1152, 1154 using point to point interface circuits 1176, 1194, 1186, 1198. Chipset 1190 also exchanges information with a high-performance graphics circuit 1138 via an interface circuit 1192 along a high-performance graphics interconnect 1139.

A shared cache (not shown) may be included in either processor or outside of both processors; yet connected with the processors via P-P interconnect, such that either or both processors' local cache information may be stored in the shared cache if a processor is placed into a low power mode.

Chipset 1190 may be coupled to a first bus 1116 via an interface 1196. In one embodiment, first bus 1116 may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another third generation I/O interconnect bus, although the scope of the present invention is not so limited.

As shown in FIG. 11, various I/O devices 1114 are coupled to first bus 1116, along with a bus bridge 1118 which couples first bus 1116 to a second bus 1120. In one embodiment, second bus 1120 includes a low pin count (LPC) bus. Various devices are coupled to second bus 1120 including, for example, a keyboard and/or mouse 1122, communication devices 1127 and a storage unit 1128 such as a disk drive or other mass storage device which often includes instructions/code and data 1130, in one embodiment. Further, an audio I/O 1124 is shown coupled to second bus 1120. Note that other architectures are possible, where the included components and interconnect architectures vary. For example, instead of the point-to-point architecture of FIG. 11, a system may implement a multi-drop bus or other such architecture.

Using the various inertial and environmental sensors present in a platform, many different use cases may be realized. These use cases enable advanced computing operations including perceptual computing and also allow for enhancements with regard to power management/battery life, security, and system responsiveness.

For example with regard to power management/battery life issues, based at least on part on information from an ambient light sensor, the ambient light conditions in a location of the platform are determined and intensity of the display controlled accordingly. Thus, power consumed in operating the display is reduced in certain light conditions.

As to security operations, based on context information obtained from the sensors such as location information, it may be determined whether a user is allowed to access certain secure documents. For example, a user may be permitted to access such documents at a work place or a home location. However, the user is prevented from accessing such documents when the platform is present at a public location. This determination, in one embodiment, is based on location information, e.g., determined via a GPS sensor or camera recognition of landmarks. Other security operations may include providing for pairing of devices within a close range of each other, e.g., a portable platform as described herein and a user's desktop computer, mobile telephone or so forth. Certain sharing, in some implementations, are realized via near field communication when these devices are so paired. However, when the devices exceed a certain range, such sharing may be disabled. Furthermore, when pairing a platform as described herein and a smartphone, an alarm may be configured to be triggered when the devices move more than a predetermined distance from each other, when in a public location. In contrast, when these paired devices are in a safe location, e.g., a work place or home location, the devices may exceed this predetermined limit without triggering such alarm.

Responsiveness may also be enhanced using the sensor information. For example, even when a platform is in a low power state, the sensors may still be enabled to run at a relatively low frequency. Accordingly, any changes in a location of the platform, e.g., as determined by inertial sensors, GPS sensor, or so forth is determined. If no such changes have been registered, a faster connection to a previous wireless hub such as a Wi-Fi™ access point or similar wireless enabler occurs, as there is no need to scan for available wireless network resources in this case. Thus, a greater level of responsiveness when waking from a low power state is achieved.

It is to be understood that many other use cases may be enabled using sensor information obtained via the integrated sensors within a platform as described herein, and the above examples are only for purposes of illustration. Using a system as described herein, a perceptual computing system may allow for the addition of alternative input modalities, including gesture recognition, and enable the system to sense user operations and intent.

In some embodiments one or more infrared or other heat sensing elements, or any other element for sensing the presence or movement of a user may be present. Such sensing elements may include multiple different elements working together, working in sequence, or both. For example, sensing elements include elements that provide initial sensing, such as light or sound projection, followed by sensing for gesture detection by, for example, an ultrasonic time of flight camera or a patterned light camera.

Also in some embodiments, the system includes a light generator to produce an illuminated line. In some embodiments, this line provides a visual cue regarding a virtual boundary, namely an imaginary or virtual location in space, where action of the user to pass or break through the virtual boundary or plane is interpreted as an intent to engage with the computing system. In some embodiments, the illuminated line may change colors as the computing system transitions into different states with regard to the user. The illuminated line may be used to provide a visual cue for the user of a virtual boundary in space, and may be used by the system to determine transitions in state of the computer with regard to the user, including determining when the user wishes to engage with the computer.

In some embodiments, the computer senses user position and operates to interpret the movement of a hand of the user through the virtual boundary as a gesture indicating an intention of the user to engage with the computer. In some embodiments, upon the user passing through the virtual line or plane the light generated by the light generator may change, thereby providing visual feedback to the user that the user has entered an area for providing gestures to provide input to the computer.

Display screens may provide visual indications of transitions of state of the computing system with regard to a user. In some embodiments, a first screen is provided in a first state in which the presence of a user is sensed by the system, such as through use of one or more of the sensing elements.

In some implementations, the system acts to sense user identity, such as by facial recognition. Here, transition to a second screen may be provided in a second state, in which the computing system has recognized the user identity, where this second the screen provides visual feedback to the user that the user has transitioned into a new state. Transition to a third screen may occur in a third state in which the user has confirmed recognition of the user.

In some embodiments, the computing system may use a transition mechanism to determine a location of a virtual boundary for a user, where the location of the virtual boundary may vary with user and context. The computing system may generate a light, such as an illuminated line, to indicate the virtual boundary for engaging with the system. In some embodiments, the computing system may be in a waiting state, and the light may be produced in a first color. The computing system may detect whether the user has reached past the virtual boundary, such as by sensing the presence and movement of the user using sensing elements.

In some embodiments, if the user has been detected as having crossed the virtual boundary (such as the hands of the user being closer to the computing system than the virtual boundary line), the computing system may transition to a state for receiving gesture inputs from the user, where a mechanism to indicate the transition may include the light indicating the virtual boundary changing to a second color.

In some embodiments, the computing system may then determine whether gesture movement is detected. If gesture movement is detected, the computing system may proceed with a gesture recognition process, which may include the use of data from a gesture data library, which may reside in memory in the computing device or may be otherwise accessed by the computing device.

If a gesture of the user is recognized, the computing system may perform a function in response to the input, and return to receive additional gestures if the user is within the virtual boundary. In some embodiments, if the gesture is not recognized, the computing system may transition into an error state, where a mechanism to indicate the error state may include the light indicating the virtual boundary changing to a third color, with the system returning to receive additional gestures if the user is within the virtual boundary for engaging with the computing system.

As mentioned above, in other embodiments the system can be configured as a convertible tablet system that can be used in at least two different modes, a tablet mode and a notebook mode. The convertible system may have two panels, namely a display panel and a base panel such that in the tablet mode the two panels are disposed in a stack on top of one another. In the tablet mode, the display panel faces outwardly and may provide touch screen functionality as found in conventional tablets. In the notebook mode, the two panels may be arranged in an open clamshell configuration.

In various embodiments, the accelerometer may be a 3-axis accelerometer having data rates of at least 50 Hz. A gyroscope may also be included, which can be a 3-axis gyroscope. In addition, an e-compass/magnetometer may be present. Also, one or more proximity sensors may be provided (e.g., for lid open to sense when a person is in proximity (or not) to the system and adjust power/performance to extend battery life). For some OS's Sensor Fusion capability including the accelerometer, gyroscope, and compass may provide enhanced features. In addition, via a sensor hub having a real-time clock (RTC), a wake from sensors mechanism may be realized to receive sensor input when a remainder of the system is in a low power state.

In some embodiments, an internal lid/display open switch or sensor to indicate when the lid is closed/open, and can be used to place the system into Connected Standby or automatically wake from Connected Standby state. Other system sensors can include ACPI sensors for internal processor, memory, and skin temperature monitoring to enable changes to processor and system operating states based on sensed parameters.

In an embodiment, the OS may be a Microsoft® Windows® 8 OS that implements Connected Standby (also referred to herein as Win8 CS). Windows 8 Connected Standby or another OS having a similar state can provide, via a platform as described herein, very low ultra idle power to enable applications to remain connected, e.g., to a cloud-based location, at very low power consumption. The platform can supports 3 power states, namely screen on (normal); Connected Standby (as a default “off” state); and shutdown (zero watts of power consumption). Thus in the Connected Standby state, the platform is logically on (at minimal power levels) even though the screen is off. In such a platform, power management can be made to be transparent to applications and maintain constant connectivity, in part due to offload technology to enable the lowest powered component to perform an operation.

Referring now to FIG. 12, a block diagram of components present in a computer system in accordance with an embodiment of the present invention is illustrated. As shown in FIG. 12, system 1200 includes any combination of components. These components may be implemented as ICs, portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in a computer system, or as components otherwise incorporated within a chassis of the computer system. Note also that the block diagram of FIG. 12 is intended to show a high level view of many components of the computer system. However, it is to be understood that some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations. As a result, the invention described above may be implemented in any portion of one or more of the interconnects illustrated or described below.

As seen in FIG. 12, a processor 1210, in one embodiment, includes a microprocessor, multi-core processor, multithreaded processor, an ultra low voltage processor, an embedded processor, or other known processing element. In the illustrated implementation, processor 1210 acts as a main processing unit and central hub for communication with many of the various components of the system 1200. As one example, processor 1200 is implemented as a system on a chip (SoC). As a specific illustrative example, processor 1210 includes an Intel® Architecture Core™-based processor such as an i3, i5, i7 or another such processor available from Intel Corporation, Santa Clara, Calif. However, understand that other low power processors such as available from Advanced Micro Devices, Inc. (AMD) of Sunnyvale, Calif., a MIPS-based design from MIPS Technologies, Inc. of Sunnyvale, Calif., an ARM-based design licensed from ARM Holdings, Ltd. or customer thereof, or their licensees or adopters may instead be present in other embodiments such as an Apple A5/A6 processor, a Qualcomm Snapdragon processor, or TI OMAP processor. Note that many of the customer versions of such processors are modified and varied; however, they may support or recognize a specific instructions set that performs defined algorithms as set forth by the processor licensor. Here, the microarchitectural implementation may vary, but the architectural function of the processor is usually consistent. Certain details regarding the architecture and operation of processor 1210 in one implementation will be discussed further below to provide an illustrative example.

Processor 1210, in one embodiment, communicates with a system memory 1215. As an illustrative example, which in an embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. As examples, the memory can be in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design such as the current LPDDR2 standard according to JEDEC JESD 209-2E (published April 2009), or a next generation LPDDR standard to be referred to as LPDDR3 or LPDDR4 that will offer extensions to LPDDR2 to increase bandwidth. In various implementations the individual memory devices may be of different package types such as single die package (SDP), dual die package (DDP) or quad die package (67P). These devices, in some embodiments, are directly soldered onto a motherboard to provide a lower profile solution, while in other embodiments the devices are configured as one or more memory modules that in turn couple to the motherboard by a given connector. And of course, other memory implementations are possible such as other types of memory modules, e.g., dual inline memory modules (DIMMs) of different varieties including but not limited to microDIMMs, MiniDIMMs. In a particular illustrative embodiment, memory is sized between 2 GB and 16 GB, and may be configured as a DDR3LM package or an LPDDR2 or LPDDR3 memory that is soldered onto a motherboard via a ball grid array (BGA).

To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage 1220 may also couple to processor 1210. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a SSD. However in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as a SSD cache to enable non-volatile storage of context state and other such information during power down events so that a fast power up can occur on re-initiation of system activities. Also shown in FIG. 12, a flash device 1222 may be coupled to processor 1210, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including a basic input/output software (BIOS) as well as other firmware of the system.

In various embodiments, mass storage of the system is implemented by a SSD alone or as a disk, optical or other drive with an SSD cache. In some embodiments, the mass storage is implemented as a SSD or as a HDD along with a restore (RST) cache module. In various implementations, the HDD provides for storage of between 320 GB-4 terabytes (TB) and upward while the RST cache is implemented with a SSD having a capacity of 24 GB-256 GB. Note that such SSD cache may be configured as a single level cache (SLC) or multi-level cache (MLC) option to provide an appropriate level of responsiveness. In a SSD-only option, the module may be accommodated in various locations such as in a mSATA or NGFF slot. As an example, an SSD has a capacity ranging from 120 GB-1 TB.

Various input/output (IO) devices may be present within system 1200. Specifically shown in the embodiment of FIG. 12 is a display 1224 which may be a high definition LCD or LED panel configured within a lid portion of the chassis. This display panel may also provide for a touch screen 1225, e.g., adapted externally over the display panel such that via a user's interaction with this touch screen, user inputs can be provided to the system to enable desired operations, e.g., with regard to the display of information, accessing of information and so forth. In one embodiment, display 1224 may be coupled to processor 1210 via a display interconnect that can be implemented as a high performance graphics interconnect. Touch screen 1225 may be coupled to processor 1210 via another interconnect, which in an embodiment can be an I2C interconnect. As further shown in FIG. 12, in addition to touch screen 1225, user input by way of touch can also occur via a touch pad 1230 which may be configured within the chassis and may also be coupled to the same I2C interconnect as touch screen 1225.

The display panel may operate in multiple modes. In a first mode, the display panel can be arranged in a transparent state in which the display panel is transparent to visible light. In various embodiments, the majority of the display panel may be a display except for a bezel around the periphery. When the system is operated in a notebook mode and the display panel is operated in a transparent state, a user may view information that is presented on the display panel while also being able to view objects behind the display. In addition, information displayed on the display panel may be viewed by a user positioned behind the display. Or the operating state of the display panel can be an opaque state in which visible light does not transmit through the display panel.

In a tablet mode the system is folded shut such that the back display surface of the display panel comes to rest in a position such that it faces outwardly towards a user, when the bottom surface of the base panel is rested on a surface or held by the user. In the tablet mode of operation, the back display surface performs the role of a display and user interface, as this surface may have touch screen functionality and may perform other known functions of a conventional touch screen device, such as a tablet device. To this end, the display panel may include a transparency-adjusting layer that is disposed between a touch screen layer and a front display surface. In some embodiments the transparency-adjusting layer may be an electrochromic layer (EC), a LCD layer, or a combination of EC and LCD layers.

In various embodiments, the display can be of different sizes, e.g., an 11.6″ or a 13.3″ screen, and may have a 16:9 aspect ratio, and at least 300 nits brightness. Also the display may be of full high definition (HD) resolution (at least 1920×1080p), be compatible with an embedded display port (eDP), and be a low power panel with panel self refresh.

As to touch screen capabilities, the system may provide for a display multi-touch panel that is multi-touch capacitive and being at least 5 finger capable. And in some embodiments, the display may be 10 finger capable. In one embodiment, the touch screen is accommodated within a damage and scratch-resistant glass and coating (e.g., Gorilla Glass™ or Gorilla Glass 2™) for low friction to reduce “finger burn” and avoid “finger skipping”. To provide for an enhanced touch experience and responsiveness, the touch panel, in some implementations, has multi-touch functionality, such as less than 2 frames (30 Hz) per static view during pinch zoom, and single-touch functionality of less than 1 cm per frame (30 Hz) with 200 ms (lag on finger to pointer). The display, in some implementations, supports edge-to-edge glass with a minimal screen bezel that is also flush with the panel surface, and limited IO interference when using multi-touch.

For perceptual computing and other purposes, various sensors may be present within the system and may be coupled to processor 1210 in different manners. Certain inertial and environmental sensors may couple to processor 1210 through a sensor hub 1240, e.g., via an I2C interconnect. In the embodiment shown in FIG. 12, these sensors may include an accelerometer 1241, an ambient light sensor (ALS) 1242, a compass 1243 and a gyroscope 1244. Other environmental sensors may include one or more thermal sensors 1246 which in some embodiments couple to processor 1210 via a system management bus (SMBus) bus.

Using the various inertial and environmental sensors present in a platform, many different use cases may be realized. These use cases enable advanced computing operations including perceptual computing and also allow for enhancements with regard to power management/battery life, security, and system responsiveness.

For example with regard to power management/battery life issues, based at least on part on information from an ambient light sensor, the ambient light conditions in a location of the platform are determined and intensity of the display controlled accordingly. Thus, power consumed in operating the display is reduced in certain light conditions.

As to security operations, based on context information obtained from the sensors such as location information, it may be determined whether a user is allowed to access certain secure documents. For example, a user may be permitted to access such documents at a work place or a home location. However, the user is prevented from accessing such documents when the platform is present at a public location. This determination, in one embodiment, is based on location information, e.g., determined via a GPS sensor or camera recognition of landmarks. Other security operations may include providing for pairing of devices within a close range of each other, e.g., a portable platform as described herein and a user's desktop computer, mobile telephone or so forth. Certain sharing, in some implementations, are realized via near field communication when these devices are so paired. However, when the devices exceed a certain range, such sharing may be disabled.

Furthermore, when pairing a platform as described herein and a smartphone, an alarm may be configured to be triggered when the devices move more than a predetermined distance from each other, when in a public location. In contrast, when these paired devices are in a safe location, e.g., a work place or home location, the devices may exceed this predetermined limit without triggering such alarm.

Responsiveness may also be enhanced using the sensor information. For example, even when a platform is in a low power state, the sensors may still be enabled to run at a relatively low frequency. Accordingly, any changes in a location of the platform, e.g., as determined by inertial sensors, GPS sensor, or so forth is determined. If no such changes have been registered, a faster connection to a previous wireless hub such as a Wi-Fi™ access point or similar wireless enabler occurs, as there is no need to scan for available wireless network resources in this case. Thus, a greater level of responsiveness when waking from a low power state is achieved.

It is to be understood that many other use cases may be enabled using sensor information obtained via the integrated sensors within a platform as described herein, and the above examples are only for purposes of illustration. Using a system as described herein, a perceptual computing system may allow for the addition of alternative input modalities, including gesture recognition, and enable the system to sense user operations and intent.

In some embodiments one or more infrared or other heat sensing elements, or any other element for sensing the presence or movement of a user may be present. Such sensing elements may include multiple different elements working together, working in sequence, or both. For example, sensing elements include elements that provide initial sensing, such as light or sound projection, followed by sensing for gesture detection by, for example, an ultrasonic time of flight camera or a patterned light camera.

Also in some embodiments, the system includes a light generator to produce an illuminated line. In some embodiments, this line provides a visual cue regarding a virtual boundary, namely an imaginary or virtual location in space, where action of the user to pass or break through the virtual boundary or plane is interpreted as an intent to engage with the computing system. In some embodiments, the illuminated line may change colors as the computing system transitions into different states with regard to the user. The illuminated line may be used to provide a visual cue for the user of a virtual boundary in space, and may be used by the system to determine transitions in state of the computer with regard to the user, including determining when the user wishes to engage with the computer.

In some embodiments, the computer senses user position and operates to interpret the movement of a hand of the user through the virtual boundary as a gesture indicating an intention of the user to engage with the computer. In some embodiments, upon the user passing through the virtual line or plane the light generated by the light generator may change, thereby providing visual feedback to the user that the user has entered an area for providing gestures to provide input to the computer.

Display screens may provide visual indications of transitions of state of the computing system with regard to a user. In some embodiments, a first screen is provided in a first state in which the presence of a user is sensed by the system, such as through use of one or more of the sensing elements.

In some implementations, the system acts to sense user identity, such as by facial recognition. Here, transition to a second screen may be provided in a second state, in which the computing system has recognized the user identity, where this second the screen provides visual feedback to the user that the user has transitioned into a new state. Transition to a third screen may occur in a third state in which the user has confirmed recognition of the user.

In some embodiments, the computing system may use a transition mechanism to determine a location of a virtual boundary for a user, where the location of the virtual boundary may vary with user and context. The computing system may generate a light, such as an illuminated line, to indicate the virtual boundary for engaging with the system. In some embodiments, the computing system may be in a waiting state, and the light may be produced in a first color. The computing system may detect whether the user has reached past the virtual boundary, such as by sensing the presence and movement of the user using sensing elements.

In some embodiments, if the user has been detected as having crossed the virtual boundary (such as the hands of the user being closer to the computing system than the virtual boundary line), the computing system may transition to a state for receiving gesture inputs from the user, where a mechanism to indicate the transition may include the light indicating the virtual boundary changing to a second color.

In some embodiments, the computing system may then determine whether gesture movement is detected. If gesture movement is detected, the computing system may proceed with a gesture recognition process, which may include the use of data from a gesture data library, which may reside in memory in the computing device or may be otherwise accessed by the computing device.

If a gesture of the user is recognized, the computing system may perform a function in response to the input, and return to receive additional gestures if the user is within the virtual boundary. In some embodiments, if the gesture is not recognized, the computing system may transition into an error state, where a mechanism to indicate the error state may include the light indicating the virtual boundary changing to a third color, with the system returning to receive additional gestures if the user is within the virtual boundary for engaging with the computing system.

As mentioned above, in other embodiments the system can be configured as a convertible tablet system that can be used in at least two different modes, a tablet mode and a notebook mode. The convertible system may have two panels, namely a display panel and a base panel such that in the tablet mode the two panels are disposed in a stack on top of one another. In the tablet mode, the display panel faces outwardly and may provide touch screen functionality as found in conventional tablets. In the notebook mode, the two panels may be arranged in an open clamshell configuration.

In various embodiments, the accelerometer may be a 3-axis accelerometer having data rates of at least 50 Hz. A gyroscope may also be included, which can be a 3-axis gyroscope. In addition, an e-compass/magnetometer may be present. Also, one or more proximity sensors may be provided (e.g., for lid open to sense when a person is in proximity (or not) to the system and adjust power/performance to extend battery life). For some OS's Sensor Fusion capability including the accelerometer, gyroscope, and compass may provide enhanced features. In addition, via a sensor hub having a real-time clock (RTC), a wake from sensors mechanism may be realized to receive sensor input when a remainder of the system is in a low power state.

In some embodiments, an internal lid/display open switch or sensor to indicate when the lid is closed/open, and can be used to place the system into Connected Standby or automatically wake from Connected Standby state. Other system sensors can include ACPI sensors for internal processor, memory, and skin temperature monitoring to enable changes to processor and system operating states based on sensed parameters.

In an embodiment, the OS may be a Microsoft® Windows® 8 OS that implements Connected Standby (also referred to herein as Win8 CS). Windows 8 Connected Standby or another OS having a similar state can provide, via a platform as described herein, very low ultra idle power to enable applications to remain connected, e.g., to a cloud-based location, at very low power consumption. The platform can supports 3 power states, namely screen on (normal); Connected Standby (as a default “off” state); and shutdown (zero watts of power consumption). Thus in the Connected Standby state, the platform is logically on (at minimal power levels) even though the screen is off. In such a platform, power management can be made to be transparent to applications and maintain constant connectivity, in part due to offload technology to enable the lowest powered component to perform an operation.

Also seen in FIG. 12, various peripheral devices may couple to processor 1210 via a low pin count (LPC) interconnect. In the embodiment shown, various components can be coupled through an embedded controller 1235. Such components can include a keyboard 1236 (e.g., coupled via a PS2 interface), a fan 1237, and a thermal sensor 1239. In some embodiments, touch pad 1230 may also couple to EC 1235 via a PS2 interface. In addition, a security processor such as a trusted platform module (TPM) 1238 in accordance with the Trusted Computing Group (TCG) TPM Specification Version 1.2, dated Oct. 2, 2003, may also couple to processor 1210 via this LPC interconnect. However, understand the scope of the present invention is not limited in this regard and secure processing and storage of secure information may be in another protected location such as a static random access memory (SRAM) in a security coprocessor, or as encrypted data blobs that are only decrypted when protected by a secure enclave (SE) processor mode.

In a particular implementation, peripheral ports may include a high definition media interface (HDMI) connector (which can be of different form factors such as full size, mini or micro); one or more USB ports, such as full-size external ports in accordance with the Universal Serial Bus Revision 3.0 Specification (November 2008), with at least one powered for charging of USB devices (such as smartphones) when the system is in Connected Standby state and is plugged into AC wall power. In addition, one or more Thunderbolt™ ports can be provided. Other ports may include an externally accessible card reader such as a full size SD-XC card reader and/or a SIM card reader for WWAN (e.g., an 8 pin card reader). For audio, a 3.5 mm jack with stereo sound and microphone capability (e.g., combination functionality) can be present, with support for jack detection (e.g., headphone only support using microphone in the lid or headphone with microphone in cable). In some embodiments, this jack can be re-taskable between stereo headphone and stereo microphone input. Also, a power jack can be provided for coupling to an AC brick.

System 1200 can communicate with external devices in a variety of manners, including wirelessly. In the embodiment shown in FIG. 12, various wireless modules, each of which can correspond to a radio configured for a particular wireless communication protocol, are present. One manner for wireless communication in a short range such as a near field may be via a near field communication (NFC) unit 1245 which may communicate, in one embodiment with processor 1210 via an SMBus. Note that via this NFC unit 1245, devices in close proximity to each other can communicate. For example, a user can enable system 1200 to communicate with another (e.g.,) portable device such as a smartphone of the user via adapting the two devices together in close relation and enabling transfer of information such as identification information payment information, data such as image data or so forth. Wireless power transfer may also be performed using a NFC system.

Using the NFC unit described herein, users can bump devices side-to-side and place devices side-by-side for near field coupling functions (such as near field communication and wireless power transfer (WPT)) by leveraging the coupling between coils of one or more of such devices. More specifically, embodiments provide devices with strategically shaped, and placed, ferrite materials, to provide for better coupling of the coils. Each coil has an inductance associated with it, which can be chosen in conjunction with the resistive, capacitive, and other features of the system to enable a common resonant frequency for the system.

As further seen in FIG. 12, additional wireless units can include other short range wireless engines including a WLAN unit 1250 and a Bluetooth unit 1252. Using WLAN unit 1250, Wi-Fi™ communications in accordance with a given Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard can be realized, while via Bluetooth unit 1252, short range communications via a Bluetooth protocol can occur. These units may communicate with processor 1210 via, e.g., a USB link or a universal asynchronous receiver transmitter (UART) link. Or these units may couple to processor 1210 via an interconnect according to a Peripheral Component Interconnect Express™ (PCIe™) protocol, e.g., in accordance with the PCI Express™ Specification Base Specification version 3.0 (published Jan. 17, 2007), or another such protocol such as a serial data input/output (SDIO) standard. Of course, the actual physical connection between these peripheral devices, which may be configured on one or more add-in cards, can be by way of the NGFF connectors adapted to a motherboard.

In addition, wireless wide area communications, e.g., according to a cellular or other wireless wide area protocol, can occur via a WWAN unit 1256 which in turn may couple to a subscriber identity module (SIM) 1257. In addition, to enable receipt and use of location information, a GPS module 1255 may also be present. Note that in the embodiment shown in FIG. 12, WWAN unit 1256 and an integrated capture device such as a camera module 1254 may communicate via a given USB protocol such as a USB 2.0 or 3.0 link, or a UART or I2C protocol. Again the actual physical connection of these units can be via adaptation of a NGFF add-in card to an NGFF connector configured on the motherboard.

In a particular embodiment, wireless functionality can be provided modularly, e.g., with a WiFi™ 802.11ac solution (e.g., add-in card that is backward compatible with IEEE 802.11abgn) with support for Windows 8 CS. This card can be configured in an internal slot (e.g., via an NGFF adapter). An additional module may provide for Bluetooth capability (e.g., Bluetooth 4.0 with backwards compatibility) as well as Intel® Wireless Display functionality. In addition NFC support may be provided via a separate device or multi-function device, and can be positioned as an example, in a front right portion of the chassis for easy access. A still additional module may be a WWAN device that can provide support for 3G/4G/LTE and GPS. This module can be implemented in an internal (e.g., NGFF) slot. Integrated antenna support can be provided for WiFi™, Bluetooth, WWAN, NFC and GPS, enabling seamless transition from WiFi™ to WWAN radios, wireless gigabit (WiGig) in accordance with the Wireless Gigabit Specification (July 2010), and vice versa.

As described above, an integrated camera can be incorporated in the lid. As one example, this camera can be a high resolution camera, e.g., having a resolution of at least 2.0 megapixels (MP) and extending to 6.0 MP and beyond.

To provide for audio inputs and outputs, an audio processor can be implemented via a digital signal processor (DSP) 1260, which may couple to processor 1210 via a high definition audio (HDA) link. Similarly, DSP 1260 may communicate with an integrated coder/decoder (CODEC) and amplifier 1262 that in turn may couple to output speakers 1263 which may be implemented within the chassis. Similarly, amplifier and CODEC 1262 can be coupled to receive audio inputs from a microphone 1265 which in an embodiment can be implemented via dual array microphones (such as a digital microphone array) to provide for high quality audio inputs to enable voice-activated control of various operations within the system. Note also that audio outputs can be provided from amplifier/CODEC 1262 to a headphone jack 1264. Although shown with these particular components in the embodiment of FIG. 12, understand the scope of the present invention is not limited in this regard.

In a particular embodiment, the digital audio codec and amplifier are capable of driving the stereo headphone jack, stereo microphone jack, an internal microphone array and stereo speakers. In different implementations, the codec can be integrated into an audio DSP or coupled via an HD audio path to a peripheral controller hub (PCH). In some implementations, in addition to integrated stereo speakers, one or more bass speakers can be provided, and the speaker solution can support DTS audio.

In some embodiments, processor 1210 may be powered by an external voltage regulator (VR) and multiple internal voltage regulators that are integrated inside the processor die, referred to as fully integrated voltage regulators (FIVRs). The use of multiple FIVRs in the processor enables the grouping of components into separate power planes, such that power is regulated and supplied by the FIVR to only those components in the group. During power management, a given power plane of one FIVR may be powered down or off when the processor is placed into a certain low power state, while another power plane of another FIVR remains active, or fully powered.

In one embodiment, a sustain power plane can be used during some deep sleep states to power on the I/O pins for several I/O signals, such as the interface between the processor and a PCH, the interface with the external VR and the interface with EC 1235. This sustain power plane also powers an on-die voltage regulator that supports the on-board SRAM or other cache memory in which the processor context is stored during the sleep state. The sustain power plane is also used to power on the processor's wakeup logic that monitors and processes the various wakeup source signals.

During power management, while other power planes are powered down or off when the processor enters certain deep sleep states, the sustain power plane remains powered on to support the above-referenced components. However, this can lead to unnecessary power consumption or dissipation when those components are not needed. To this end, embodiments may provide a connected standby sleep state to maintain processor context using a dedicated power plane. In one embodiment, the connected standby sleep state facilitates processor wakeup using resources of a PCH which itself may be present in a package with the processor. In one embodiment, the connected standby sleep state facilitates sustaining processor architectural functions in the PCH until processor wakeup, this enabling turning off all of the unnecessary processor components that were previously left powered on during deep sleep states, including turning off all of the clocks. In one embodiment, the PCH contains a time stamp counter (TSC) and connected standby logic for controlling the system during the connected standby state. The integrated voltage regulator for the sustain power plane may reside on the PCH as well.

In an embodiment, during the connected standby state, an integrated voltage regulator may function as a dedicated power plane that remains powered on to support the dedicated cache memory in which the processor context is stored such as critical state variables when the processor enters the deep sleep states and connected standby state. This critical state may include state variables associated with the architectural, micro-architectural, debug state, and/or similar state variables associated with the processor.

The wakeup source signals from EC 1235 may be sent to the PCH instead of the processor during the connected standby state so that the PCH can manage the wakeup processing instead of the processor. In addition, the TSC is maintained in the PCH to facilitate sustaining processor architectural functions. Although shown with these particular components in the embodiment of FIG. 12, understand the scope of the present invention is not limited in this regard.

Power control in the processor can lead to enhanced power savings. For example, power can be dynamically allocate between cores, individual cores can change frequency/voltage, and multiple deep low power states can be provided to enable very low power consumption. In addition, dynamic control of the cores or independent core portions can provide for reduced power consumption by powering off components when they are not being used.

Some implementations may provide a specific power management IC (PMIC) to control platform power. Using this solution, a system may see very low (e.g., less than 5%) battery degradation over an extended duration (e.g., 16 hours) when in a given standby state, such as when in a Win8 Connected Standby state. In a Win8 idle state a battery life exceeding, e.g., 9 hours may be realized (e.g., at 150 nits). As to video playback, a long battery life can be realized, e.g., full HD video playback can occur for a minimum of 6 hours. A platform in one implementation may have an energy capacity of, e.g., 35 watt hours (Whr) for a Win8 CS using an SSD and (e.g.,) 40-44Whr for Win8 CS using an HDD with a RST cache configuration.

A particular implementation may provide support for 15 W nominal CPU thermal design power (TDP), with a configurable CPU TDP of up to approximately 25 W TDP design point. The platform may include minimal vents owing to the thermal features described above. In addition, the platform is pillow-friendly (in that no hot air is blowing at the user). Different maximum temperature points can be realized depending on the chassis material. In one implementation of a plastic chassis (at least having to lid or base portion of plastic), the maximum operating temperature can be 52 degrees Celsius (C). And for an implementation of a metal chassis, the maximum operating temperature can be 46° C.

In different implementations, a security module such as a TPM can be integrated into a processor or can be a discrete device such as a TPM 2.0 device. With an integrated security module, also referred to as Platform Trust Technology (PTT), BIOS/firmware can be enabled to expose certain hardware features for certain security features, including secure instructions, secure boot, Intel® Anti-Theft Technology, Intel® Identity Protection Technology, Intel® Trusted Execution Technology (TXT), and Intel® Manageability Engine Technology along with secure user interfaces such as a secure keyboard and display.

While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.

A design may go through various stages, from creation to simulation to fabrication. Data representing a design may represent the design in a number of manners. First, as is useful in simulations, the hardware may be represented using a hardware description language or another functional description language. Additionally, a circuit level model with logic and/or transistor gates may be produced at some stages of the design process. Furthermore, most designs, at some stage, reach a level of data representing the physical placement of various devices in the hardware model. In the case where conventional semiconductor fabrication techniques are used, the data representing the hardware model may be the data specifying the presence or absence of various features on different mask layers for masks used to produce the integrated circuit. In any representation of the design, the data may be stored in any form of a machine readable medium. A memory or a magnetic or optical storage such as a disc may be the machine readable medium to store information transmitted via optical or electrical wave modulated or otherwise generated to transmit such information. When an electrical carrier wave indicating or carrying the code or design is transmitted, to the extent that copying, buffering, or re-transmission of the electrical signal is performed, a new copy is made. Thus, a communication provider or a network provider may store on a tangible, machine-readable medium, at least temporarily, an article, such as information encoded into a carrier wave, embodying techniques of embodiments of the present invention.

A module as used herein refers to any combination of hardware, software, and/or firmware. As an example, a module includes hardware, such as a micro-controller, associated with a non-transitory medium to store code adapted to be executed by the micro-controller. Therefore, reference to a module, in one embodiment, refers to the hardware, which is specifically configured to recognize and/or execute the code to be held on a non-transitory medium. Furthermore, in another embodiment, use of a module refers to the non-transitory medium including the code, which is specifically adapted to be executed by the microcontroller to perform predetermined operations. And as can be inferred, in yet another embodiment, the term module (in this example) may refer to the combination of the microcontroller and the non-transitory medium. Often module boundaries that are illustrated as separate commonly vary and potentially overlap. For example, a first and a second module may share hardware, software, firmware, or a combination thereof, while potentially retaining some independent hardware, software, or firmware. In one embodiment, use of the term logic includes hardware, such as transistors, registers, or other hardware, such as programmable logic devices.

Use of the phrase ‘to’ or ‘configured to,’ in one embodiment, refers to arranging, putting together, manufacturing, offering to sell, importing and/or designing an apparatus, hardware, logic, or element to perform a designated or determined task. In this example, an apparatus or element thereof that is not operating is still ‘configured to’ perform a designated task if it is designed, coupled, and/or interconnected to perform said designated task. As a purely illustrative example, a logic gate may provide a 0 or a 1 during operation. But a logic gate ‘configured to’ provide an enable signal to a clock does not include every potential logic gate that may provide a 1 or 0. Instead, the logic gate is one coupled in some manner that during operation the 1 or 0 output is to enable the clock. Note once again that use of the term ‘configured to’ does not require operation, but instead focus on the latent state of an apparatus, hardware, and/or element, where in the latent state the apparatus, hardware, and/or element is designed to perform a particular task when the apparatus, hardware, and/or element is operating.

Furthermore, use of the phrases ‘capable of/to,’ and or ‘operable to,’ in one embodiment, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. Note as above that use of to, capable to, or operable to, in one embodiment, refers to the latent state of an apparatus, logic, hardware, and/or element, where the apparatus, logic, hardware, and/or element is not operating but is designed in such a manner to enable use of an apparatus in a specified manner.

A value, as used herein, includes any known representation of a number, a state, a logical state, or a binary logical state. Often, the use of logic levels, logic values, or logical values is also referred to as l's and 0's, which simply represents binary logic states. For example, a 1 refers to a high logic level and 0 refers to a low logic level. In one embodiment, a storage cell, such as a transistor or flash cell, may be capable of holding a single logical value or multiple logical values. However, other representations of values in computer systems have been used. For example the decimal number ten may also be represented as a binary value of 1010 and a hexadecimal letter A. Therefore, a value includes any representation of information capable of being held in a computer system.

Moreover, states may be represented by values or portions of values. As an example, a first value, such as a logical one, may represent a default or initial state, while a second value, such as a logical zero, may represent a non-default state. In addition, the terms reset and set, in one embodiment, refer to a default and an updated value or state, respectively. For example, a default value potentially includes a high logical value, i.e. reset, while an updated value potentially includes a low logical value, i.e. set. Note that any combination of values may be utilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code set forth above may be implemented via instructions or code stored on a machine-accessible, machine readable, computer accessible, or computer readable medium which are executable by a processing element. A non-transitory machine-accessible/readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine, such as a computer or electronic system. For example, a non-transitory machine-accessible medium includes random-access memory (RAM), such as static RAM (SRAM) or dynamic RAM (DRAM); ROM; magnetic or optical storage medium; flash memory devices; electrical storage devices; optical storage devices; acoustical storage devices; other form of storage devices for holding information received from transitory (propagated) signals (e.g., carrier waves, infrared signals, digital signals); etc, which are to be distinguished from the non-transitory mediums that may receive information there from.

Instructions used to program logic to perform embodiments of the invention may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer)

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In the foregoing specification, a detailed description has been given with reference to specific exemplary embodiments. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. Furthermore, the foregoing use of embodiment and other exemplarily language does not necessarily refer to the same embodiment or the same example, but may refer to different and distinct embodiments, as well as potentially the same embodiment.

The systems, methods, and apparatuses can include one or a combination of the following examples:

Example 1 is a method for configuring a downstream component connected to a host component across a Peripheral Component Interconnect Express (PCIe)-compliant link, the method including receiving, from the downstream component, an indication of an extended capability; determining, from the indication, one or more configuration parameters for the downstream component; applying the one or more configuration parameters; and performing data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters.

Example 2 may include the subject matter of example 1, wherein receiving the indication of the extended capability comprises receiving a Designated Vendor Specific Extended Capability (DVSEC) definition.

Example 3 may include the subject matter of any of examples 1-2, wherein the indication of the extended capability comprises an indication of a number of buses that the downstream component will use to perform data signal and control signal transmissions.

Example 4 may include the subject matter of any of examples 1-3, and can also include allocating a number of buses for the downstream component based on the received indication of the extended capability.

Example 5 may include the subject matter of any of examples 1-4, wherein the indication of the extended capability comprises an indication of a type of a port on the downstream connected device that is connected to the host component.

Example 6 may include the subject matter of any of examples 1-5, further comprising applying one or more software policies based on the type of port indicated by the indication of the extended capability.

Example 7 may include the subject matter of any of examples 1-6, wherein the indication of the extended capability comprises an indication that the downstream component supports a D3Cold power management sub-state.

Example 8 may include the subject matter of any of examples 1-7, further comprising applying one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.

Example 9 may include the subject matter of any of examples 1-8, wherein the indication of the extended capability comprises an indication that the downstream component comprises a host router.

Example 10 may include the subject matter of any of examples 1-9, further comprising applying one or more security policies for the downstream component based on the indication that the downstream component is an host router.

Example 11 may include the subject matter of any of examples 1-10, wherein downstream port is a first downstream port, the indication that the downstream component is a host router indicates that the host router is an externally facing port, the method further comprising rejecting a second indication that a second downstream port, downstream of the first downstream port, is a host router.

Example 12 may include the subject matter of any of examples 1-11, wherein the indication of the extended capability comprises an indication that the downstream component uses a safe eject feature.

Example 13 may include the subject matter of any of examples 1-12, the method further comprising augmenting a user interface to provide a safe eject indication and a description of the downstream component to allow a user to perform a safe eject procedure prior to removing the downstream component.

Example 14 may include the subject matter of any of examples 1-14, wherein the indication of the extended capability comprises an indication that the downstream component comprises a port expandability feature to facilitate daisy-chaining of further downstream components.

Example 15 is a computer program product tangibly embodied on non-transitory computer-readable media, the computer program product comprising instructions that when executed cause logic embodied on a root port controller compliant with a Peripheral Component Interconnect Express (PCIe) protocol to receive, from the downstream component, an indication of an extended capability; determine, from the indication, one or more configuration parameters for the downstream component; apply the one or more configuration parameters; and perform data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters.

Example 16 may include the subject matter of example 15, wherein receiving the indication of the extended capability comprises receiving a Designated Vendor Specific Extended Capability (DVSEC) definition.

Example 17 may include the subject matter of any of examples 15-16, wherein the indication of the extended capability comprises an indication of a number of buses that the downstream component will use to perform data signal and control signal transmissions.

Example 18 may include the subject matter of any of examples 15-17, the instructions to allocate a number of buses for the downstream component based on the received indication of the extended capability.

Example 19 may include the subject matter of any of examples 15-18, wherein the indication of the extended capability comprises an indication of a type of a port on the downstream connected device that is connected to the host component.

Example 20 may include the subject matter of any of examples 15-19, the instructions to apply one or more software policies based on the type of port indicated by the indication of the extended capability.

Example 21 may include the subject matter of any of examples 15-20, wherein the indication of the extended capability comprises an indication that the downstream component supports a D3Cold power management sub-state.

Example 22 may include the subject matter of any of examples 15-21, the instructions to apply one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.

Example 23 may include the subject matter of any of examples 15-22, wherein the indication of the extended capability comprises an indication that the downstream component comprises a host router.

Example 24 may include the subject matter of any of examples 15-23, the instructions to apply one or more security policies for the downstream component based on the indication that the downstream component is an host router.

Example 25 may include the subject matter of any of examples 15-24, wherein the downstream port is a first downstream port, the indication that the downstream component is a host router indicates that the host router is an externally facing port, the method further comprising rejecting a second indication that a second downstream port, downstream of the first downstream port, is a host router.

Example 26 may include the subject matter of any of examples 15-25, wherein the indication of the extended capability comprises an indication that the downstream component uses a safe eject feature.

Example 27 may include the subject matter of any of examples 15-26, the instructions to augment a user interface to provide a safe eject indication and a description of the downstream component to allow a user to perform a safe eject procedure prior to removing the downstream component.

Example 28 may include the subject matter of any of examples 15-27, wherein the indication of the extended capability comprises an indication that the downstream component comprises a port expandability feature to facilitate daisy-chaining of further downstream components.

Example 29 is a system that includes a root port compliant with a Peripheral Component Interconnect Express (PCIe) protocol, the root port comprising a root port controller; and a downstream component connected to the root port across a link compliant with the PCIe protocol, the root port comprising an upstream port, and at least one hot plug-capable downstream port, the at least one hot plug-capable downstream port coupled to the component by the link based on the PCIe protocol, the hot plug-capable downstream port comprising logic implemented at least partially in hardware, the logic to receive, from the downstream component, an indication of an extended capability; determine, from the indication, one or more configuration parameters for the downstream component; apply the one or more configuration parameters; and perform data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters.

Example 30 may include the subject matter of example 29, wherein receiving the indication of the extended capability comprises receiving a Designated Vendor Specific Extended Capability (DVSEC) definition.

Example 31 may include the subject matter of any of examples 29-30, wherein the indication of the extended capability comprises an indication of a number of buses that the downstream component will use to perform data signal and control signal transmissions.

Example 32 may include the subject matter of any of examples 29-31, the logic to allocate a number of buses for the downstream component based on the received indication of the extended capability.

Example 33 may include the subject matter of any of examples 29-32, wherein the indication of the extended capability comprises an indication of a type of a port on the downstream connected device that is connected to the host component.

Example 34 may include the subject matter of any of examples 29-33, the logic to apply one or more software policies based on the type of port indicated by the indication of the extended capability.

Example 35 may include the subject matter of any of examples 29-34, wherein the indication of the extended capability comprises an indication that the downstream component supports a D3Cold power management sub-state.

Example 36 may include the subject matter of any of examples 29-35, the logic to apply one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.

Example 37 may include the subject matter of any of examples 29-36, wherein the indication of the extended capability comprises an indication that the downstream component comprises a host router.

Example 38 may include the subject matter of any of examples 26-37, the logic to apply one or more security policies for the downstream component based on the indication that the downstream component is an host router.

Example 39 may include the subject matter of any of examples 29-38, wherein downstream port is a first downstream port, the indication that the downstream component is a host router indicates that the host router is an externally facing port, the method further comprising rejecting a second indication that a second downstream port, downstream of the first downstream port, is a host router.

Example 40 may include the subject matter of any of examples 29-39, wherein the indication of the extended capability comprises an indication that the downstream component uses a safe eject feature.

Example 41 may include the subject matter of any of examples 29-40, the logic to augment a user interface to provide a safe eject indication and a description of the downstream component to allow a user to perform a safe eject procedure prior to removing the downstream component.

Example 42 may include the subject matter of any of examples 29-40, wherein the indication of the extended capability comprises an indication that the downstream component comprises a port expandability feature to facilitate daisy-chaining of further downstream components.

Example 43 is a root apparatus compliant with a Peripheral Component Interconnect Express (PCIe) protocol, the root port comprising a root port controller that includes a means for receiving, from the downstream component, an indication of an extended capability; a means for determining, from the indication, one or more configuration parameters for the downstream component; a means for applying the one or more configuration parameters; and a means for performing data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters.

Example 44 may include the subject matter of example 43, wherein receiving the indication of the extended capability comprises receiving a Designated Vendor Specific Extended Capability (DVSEC) definition.

Example 45 may include the subject matter of any of examples 43-44, wherein the indication of the extended capability comprises an indication of a number of buses that the downstream component will use to perform data signal and control signal transmissions.

Example 46 may include the subject matter of any of examples 43-45, further comprising means for allocating a number of buses for the downstream component based on the received indication of the extended capability.

Example 47 may include the subject matter of any of examples 43-46, wherein the indication of the extended capability comprises an indication of a type of a port on the downstream connected device that is connected to the host component.

Example 48 may include the subject matter of any of examples 43-47, further comprising means for applying one or more software policies based on the type of port indicated by the indication of the extended capability.

Example 49 may include the subject matter of any of examples 43-48, wherein the indication of the extended capability comprises an indication that the downstream component supports a D3Cold power management sub-state.

Example 50 may include the subject matter of any of examples 43-49, further comprising means for applying one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.

Example 51 may include the subject matter of any of examples 43-50, wherein the indication of the extended capability comprises an indication that the downstream component comprises a host router.

Example 52 may include the subject matter of any of examples 43-51, further comprising means for applying one or more security policies for the downstream component based on the indication that the downstream component is an host router.

Example 53 may include the subject matter of any of examples 43-52, wherein downstream port is a first downstream port, the indication that the downstream component is a host router indicates that the host router is an externally facing port, the method further comprising rejecting a second indication that a second downstream port, downstream of the first downstream port, is a host router.

Example 54 may include the subject matter of any of examples 43-53, wherein the indication of the extended capability comprises an indication that the downstream component uses a safe eject feature.

Example 55 may include the subject matter of any of examples 43-54, further comprising means for augmenting a user interface to provide a safe eject indication and a description of the downstream component to allow a user to perform a safe eject procedure prior to removing the downstream component.

Example 56 may include the subject matter of any of examples 43-55, wherein the indication of the extended capability comprises an indication that the downstream component comprises a port expandability feature to facilitate daisy-chaining of further downstream components.

Example 57 is a apparatus compatible with a PCIe-based protocol, the port can be an upstream component of a PCIe root complex, such as a root port or an upstream switch. The apparatus can support hot-plug capabilities. The apparatus can include one or more downstream ports coupled to an upstream port. The at least one downstream port can be a hot plug-capable downstream port. The hot plug-capable downstream port can be configured to be coupled to a downstream component via a hot plug connection. The downstream component can provide extended capabilities information to the apparatus via the hot plug-capable downstream port. The extended capabilities information can be received by the apparatus as a vendor-specific extended capabilities indication that identifies one or more register settings that correspond to and expose one or more extended capabilities that the downstream component can use. The apparatus can determine, from the indication, one or more configuration parameters for the connected downstream component. The apparatus can apply the configuration parameters and perform data signal and/or control signal transmissions across the PCIe link with the downstream component using the applied configuration parameters.

Example 58 may include the subject matter of example 57, wherein receiving the indication of the extended capability comprises receiving a Designated Vendor Specific Extended Capability (DVSEC) capabilities definition.

Example 59 may include the subject matter of any of examples 57 or 58, wherein the component is a first component and the indication of the extended capability comprises an indication of a number of buses that a second component connected first component will use to perform data signal and control signal transmissions; further comprising allocating a number of buses for the second component based on the received indication of the extended capability.

Example 60 may include the subject matter of any of examples 57-59, wherein the indication of the extended capability comprises an indication of a type of a port on the connected device that is connected to the downstream port; further comprising applying one or more software policies based on the type of port indicated by the indication of the extended capability.

Example 61 may include the subject matter of any of examples 57-60, wherein the indication of the extended capability comprises an indication that the component supports a D3Cold power management sub-state; further comprising applying one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.

Example 62 may include the subject matter of any of examples 57-61, wherein the indication of the extended capability comprises an indication that the component comprises a host router; further comprising applying one or more policies for the downstream component based on the indication that the component is an host router.

Example 63 may include the subject matter of any of examples 57-62, wherein downstream port is a first downstream port, the indication that the component is a host router indicates that the host router is an externally facing port, the method further comprising rejecting a second indication that a second downstream port, downstream of the first downstream port, is a host router.

Example 64 may include the subject matter of any of examples 57-63, wherein the indication of the extended capability comprises an indication that the component uses a safe eject feature; further comprising augmenting a user interface to provide a safe eject indication and a description of the component to allow a user to perform a safe eject procedure prior to removing the component.

Example 65 may include the subject matter of any of examples 57-64, wherein the indication of the extended capability comprises an indication that the component comprises a port expandability feature to facilitate daisy-chaining of further components; the port further comprising reserving one or more system resources for further components connected to the component device. 

What is claimed is:
 1. An apparatus comprising: an upstream port; and a hot plug-capable downstream port, the hot plug-capable downstream port configured to receive a downstream connected device without powering down, the hot plug-capable downstream port connected to a downstream component across a link compatible with a Peripheral Component Interconnect Express (PCIe)-based protocol, logic, implemented at least in part in hardware circuitry, to: identify, from the downstream component, an indication of a Designated Vendor Specific Extended Capability (DVSEC) extended capability definition that defines one or more vendor-specific features for the downstream component; determine, from the indication, one or more configuration parameters for the downstream component; and perform data signal or control signal transmissions across the PCIe-compliant link with the downstream component based, at least in part, on the applied one or more configuration parameters; wherein the indication of the DVSEC extended capability definition comprises an indication of a type of a port on the downstream connected device that is connected to the hot plug-capable downstream port; the apparatus to apply one or more software policies based on the type of port indicated by the indication of the extended capability.
 2. The apparatus of claim 1, further comprising logic, implemented at least in part in hardware circuitry, to apply the DVSEC extended capability definition to one or both of the hot plug-capable downstream port or the downstream connected device.
 3. The apparatus of claim 1, wherein the downstream component is a first component and the indication of the DVSEC extended capability definition comprises an indication of a number of buses that a second component connected to the first component will use to perform data signal and control signal transmissions; the apparatus to allocate a number of buses for the second component based on the received indication of the extended capability.
 4. The apparatus of claim 1, wherein the indication of the DVSEC extended capability definition comprises an indication that the downstream component supports a D3Cold power management sub-state; the apparatus to apply one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.
 5. The apparatus of claim 1, wherein the indication of the DVSEC extended capability definition comprises an indication that the downstream component comprises a host router; the apparatus to apply one or more policies for the downstream component based on the indication that the downstream component is an host router.
 6. The apparatus of claim 5, wherein the hot plug-capable downstream port is a first downstream port, the indication that the downstream component is a host router indicates that the host router comprises an externally facing port, the apparatus to reject a second indication that a second downstream component, downstream of the first downstream port, is a host router.
 7. The apparatus of claim 1, wherein the indication of the DVSEC extended capability definition comprises an indication that the downstream component uses a safe eject feature; the apparatus to augment a user interface to provide a safe eject indication and a description of the downstream component to allow a user to perform a safe eject procedure prior to removing the downstream component.
 8. The apparatus of claim 1, wherein the indication of the DVSEC extended capability definition comprises an indication that the downstream component comprises a port expandability feature to facilitate daisy-chaining of further components; the apparatus to reserve one or more system resources for further downstream components connected to the downstream device.
 9. A computer program product tangibly embodied on non-transitory computer-readable media, the computer program product comprising instructions that when executed cause logic embodied on a host device compatible with a Peripheral Component Interconnect Express (PCIe)-based protocol to: receive, from a component connected to a downstream port of the host device, an indication of a Designated Vendor Specific Extended Capability (DVSEC) extended capability definition that defines one or more vendor-specific features for the component; determine, from the indication, one or more configuration parameters for the component; and perform data signal or control signal transmissions across the PCIe-compliant link with the component based, at least in part, on the applied one or more configuration parameters; wherein the indication of the DVSEC extended capability definition comprises an indication of a type of a port on the downstream connected device that is connected to the host component; the instructions to apply one or more software policies based on the type of port indicated by the indication of the extended capability.
 10. The computer program product of claim 9, further comprising applying the DVSEC capabilities definition to one or both of the downstream port or the downstream connected device.
 11. The computer program product of claim 9, wherein the component is a first component and the indication of the extended capability comprises an indication of a number of buses that a second component connected downstream of the first component will use to perform data signal and control signal transmissions; the instructions to allocate a number of buses for the component based on the received indication of the DVSEC extended capability definition.
 12. The computer program product of claim 9, wherein the indication of the DVSEC extended capability definition comprises an indication that the component supports a D3Cold power management sub-state; the instructions to apply one or more runtime power management mechanisms to allow the component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.
 13. The computer program product of claim 9, wherein the indication of the DVSEC extended capability definition comprises an indication that the component comprises a host router; the instructions to apply one or more security policies for the component based on the indication that the component is an host router.
 14. The computer program product of claim 13, wherein the downstream port is a first downstream port, the indication that the component is a host router indicates that the host router comprises an externally facing port, the instructions to reject a second indication that a second downstream component, downstream of the first downstream port, is a host router.
 15. The computer program product of claim 9, wherein the indication of the DVSEC extended capability definition comprises an indication that the component uses a safe eject feature; the instructions to augment a user interface to provide a safe eject indication and a description of the component to allow a user to perform a safe eject procedure prior to removing the component.
 16. The computer program product of claim 9, wherein the indication of the DVSEC extended capability definition comprises an indication that the component comprises a port expandability feature to facilitate daisy-chaining of further components, the instructions to reserve one or more system resources for further components connected to the component device.
 17. A system comprising: a root port compatible with a Peripheral Component Interconnect Express (PCIe)-based protocol, the root port comprising a root port controller; and a component connected to the root port across a link based on the PCIe protocol, the root port comprising: an upstream port, and at least one hot plug-capable downstream port, the hot plug-capable downstream port configured to receive a downstream connected device without powering down, the at least one hot plug-capable downstream port coupled to the component by the link based on the PCIe protocol, the hot plug-capable downstream port comprising logic implemented at least partially in hardware, the logic to: receive, from the component, an indication of a Designated Vendor Specific Extended Capability (DVSEC) extended capability definition that defines one or more vendor-specific features for the component; determine, from the indication, one or more configuration parameters for the component; perform data signal or control signal transmissions across the PCIe-compliant link with the component based, at least in part, on the applied one or more configuration parameters; wherein the indication of the DVSEC extended capability definition comprises an indication of a type of a port on the downstream connected device that is connected to the root port; the logic to apply one or more software policies based on the type of port indicated by the indication of the extended capability.
 18. The system of claim 17, wherein the at least one hot plug-capable downstream port is compatible with a converged input/output (CIO)-based or a universal serial bus (USB)-based protocol.
 19. The system of claim 17, wherein the component is a first component and the indication of the extended capability comprises an indication of a number of buses that the first component will use to perform data signal and control signal transmissions; the logic to allocate a number of buses for a second component connected downstream of the first component based on the received indication of the DVSEC extended capability definition.
 20. The system of claim 17, wherein the indication of the DVSEC extended capability definition comprises an indication that the component supports a D3Cold power management sub-state; the logic to apply one or more runtime power management mechanisms to allow the downstream component to enter and exit the D3Cold power management sub-state and to enter a D0 power state at an exit of the D3Cold power management sub-state.
 21. The system of claim 17, wherein the indication of the DVSEC extended capability definition comprises an indication that the downstream component comprises a host router; the logic to apply one or more security policies for the component based on the indication that the downstream component is an host router.
 22. The system of claim 21, wherein the hot plug-capable downstream port is a first downstream port, the indication that the component is a host router indicates that the host router comprises an externally facing port, the method further comprising rejecting a second indication that a second downstream component, downstream of the first downstream port, is a host router. 